Token导航 LogoToken导航TokenDH.com
研究检索需要联网clawhub未标认证来源可访问clear审计提醒

productboard-release产品板发布

Agent Skill

productboard-release 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

58,685

周安装

2,374

GitHub Stars

1

下载量

18,422
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:productboard-release(产品板发布)
来源仓库:https://github.com/robertoamoreno/productboard-release
安装命令:
openclaw skills install productboard-release
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install productboard-release

简介

管理 ProductBoard 版本规划与路线图。

  • 适用于 OpenClaw 中与产品管理工具深度集成。
  • 支持版本发布、里程碑设置与进度跟踪。productboard-release 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 安装命令:openclaw skills install productboard-release。
  • 需绑定有效 API 凭证并控制写权限范围。

SKILL.md

name
productboard-release
description
Manage ProductBoard releases and roadmap planning
user-invocable
false
homepage
https://github.com/robertoamoreno/openclaw-productboard
metadata
{"openclaw":{"emoji":"🚀"}}

ProductBoard Release Planning Skill

Plan and manage product releases by organizing features, tracking progress, and updating statuses in ProductBoard.

Available Tools

  • pb_feature_create - Create new features for releases
  • pb_feature_update - Update feature status and details
  • pb_feature_list - List features by status or product
  • pb_feature_get - Get detailed feature information
  • pb_product_list - List products
  • pb_product_hierarchy - View product structure
  • pb_user_list - Find users to assign as owners

Release Planning Workflow

1. Review Current State

1. pb_product_hierarchy - Understand workspace structure
2. pb_feature_list with status "candidate" - Review feature candidates
3. pb_feature_list with status "in-progress" - Check ongoing work

2. Prioritize Features

Review candidates and update their status:

pb_feature_update:
  - id: "feature-id"
  - status: "in-progress"  // Move to active development

3. Assign Owners

Find users and assign feature ownership:

1. pb_user_list - Get available team members
2. pb_feature_update:
   - id: "feature-id"
   - ownerEmail: "developer@company.com"

4. Set Timeframes

Add planning dates to features:

pb_feature_update:
  - id: "feature-id"
  - startDate: "2024-01-15"
  - endDate: "2024-02-15"

5. Track Progress

Monitor feature statuses:

pb_feature_list with status "in-progress" - Active development
pb_feature_list with status "shipped" - Completed features

Feature Status Lifecycle

StatusDescription
newJust created, not yet evaluated
candidateBeing considered for development
in-progressActively being developed
shippedReleased to customers
postponedDeferred to future planning
archivedNo longer relevant

Planning Scenarios

Sprint Planning

  1. List candidates: pb_feature_list with status "candidate"
  2. Review each feature: pb_feature_get for details
  3. Move selected features to in-progress: pb_feature_update
  4. Assign owners: pb_feature_update with ownerEmail
  5. Set sprint dates: pb_feature_update with startDate/endDate

Release Retrospective

  1. List shipped features: pb_feature_list with status "shipped"
  2. Review feedback on features: Use feedback skill tools
  3. Archive completed work: pb_feature_update with status "archived"

Quarterly Planning

  1. Review product hierarchy: pb_product_hierarchy
  2. List all active features by product
  3. Reassess priorities and update statuses
  4. Create new features as needed: pb_feature_create

Organizing Features

By Product

pb_feature_create:
  - name: "Feature name"
  - productId: "product-id"
  - status: "candidate"

By Component

pb_feature_create:
  - name: "Feature name"
  - componentId: "component-id"
  - status: "candidate"

As Sub-feature

pb_feature_create:
  - name: "Sub-feature name"
  - parentFeatureId: "parent-feature-id"

Best Practices

  1. Use consistent statuses: Move features through the lifecycle systematically
  2. Assign owners early: Clear ownership improves accountability
  3. Set realistic timeframes: Update dates as plans change
  4. Organize hierarchically: Use products, components, and sub-features
  5. Archive completed work: Keep the backlog clean by archiving shipped features
  6. Review regularly: Use listing tools to audit feature states

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

74.47%
按下载量换算13,719

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

未展示

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills