技能创作工作流程
- 作者仓库星标 4,456
- 作者仓库 Product-Manager-Skills
- 领域
- 通用
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @deanpeters · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
第一阶段:预检(避免重复工作)
搜索重叠技能: 决定类型: 组件:一个工件/模板 互动:3-5 个自适应问题 + 编号选项 工作流程:多阶段编排
第 2 阶段:生成草稿
如果您有源材料: 如果您需要引导提示:
第三阶段:强化技能
手动审查: 明确的“何时使用”指导 一个具体示例 一种明确的反模式 无填充物或模糊的顾问说法
第四阶段:硬验证
在考虑提交之前运行严格的检查:
第 5 阶段:与 Repo 文档集成
如果这是一项新技能: 将其添加到正确的自述文件类别表中 更新技能总数和类别计数 验证链接路径解析
第六阶段:可选包装
如果针对克劳德自定义技能上传:
## Purpose
Create or update PM skills without chaos. This workflow turns rough notes, workshop content, or half-baked prompt dumps into compliant `skills/<skill-name>/SKILL.md` assets that actually pass validation and belong in this repo.
Use it when you want to ship a new skill without "looks good to me" roulette.
## Key Concepts
### Dogfood First
Use repo-native tools and standards before inventing a custom process:
- `scripts/find-a-skill.sh`
- `scripts/add-a-skill.sh`
- `scripts/build-a-skill.sh`
- `scripts/test-a-skill.sh`
- `scripts/check-skill-metadata.py`
### Pick the Right Creation Path
- **Guided wizard (`build-a-skill.sh`)**: Best when you have an idea but not final prose.
- **Content-first generator (`add-a-skill.sh`)**: Best when you already have source content.
- **Manual edit + validate**: Best for tightening an existing skill.
### Definition of Done (No Exceptions)
A skill is done only when:
1. Frontmatter is valid (`name`, `description`, `intent`, `type`)
2. Section order is compliant
3. Metadata limits are respected (`name` <= 64 chars, `description` <= 200 chars)
4. Description says both what the skill does and when to use it
5. Intent carries the fuller repo-facing summary without replacing the trigger-oriented description
6. Cross-references resolve
7. README catalog counts and tables are updated (if adding/removing skills)
### Facilitation Source of Truth
When running this workflow as a guided conversation, use [`workshop-facilitation`](../workshop-facilitation/SKILL.md) as the interaction protocol.
It defines:
- session heads-up + entry mode (Guided, Context dump, Best guess)
- one-question turns with plain-language prompts
- progress labels (for example, Context Qx/8 and Scoring Qx/5)
- interruption handling and pause/resume behavior
- numbered recommendations at decision points
- quick-select numbered response options for regular questions (include `Other (specify)` when useful)
This file defines the workflow sequence and domain-specific outputs. If there is a conflict, follow this file's workflow logic.
## Application
### Phase 1: Preflight (Avoid Duplicate Work)
1. Search for overlapping skills:
```bash
./scripts/find-a-skill.sh --keyword "<topic>"
```
2. Decide type:
- **Component**: one artifact/template
- **Interactive**: 3-5 adaptive questions + numbered options
- **Workflow**: multi-phase orchestration
### Phase 2: Generate Draft
If you have source material:
```bash
./scripts/add-a-skill.sh research/your-framework.md
```
If you want guided prompts:
```bash
./scripts/build-a-skill.sh
```
### Phase 3: Tighten the Skill
Manually review for:
- Clear "when to use" guidance
- One concrete example
- One explicit anti-pattern
- No filler or vague consultant-speak
### Phase 4: Validate Hard
Run strict checks before thinking about commit:
```bash
./scripts/test-a-skill.sh --skill <skill-name> --smoke
python3 scripts/check-skill-metadata.py skills/<skill-name>/SKILL.md
python3 scripts/check-skill-triggers.py skills/<skill-name>/SKILL.md --show-cases
```
### Phase 5: Integrate with Repo Docs
If this is a new skill:
1. Add it to the correct README category table
2. Update skill totals and category counts
3. Verify link paths resolve
### Phase 6: Optional Packaging
If targeting Claude custom skill upload:
```bash
./scripts/zip-a-skill.sh --skill <skill-name>
# or zip one category:
./scripts/zip-a-skill.sh --type component --output dist/skill-zips
# or use a curated starter preset:
./scripts/zip-a-skill.sh --preset core-pm --output dist/skill-zips
```
## Examples
### Example: Turn Workshop Notes into a Skill
Input: `research/pricing-workshop-notes.md`
Goal: new interactive advisor
```bash
./scripts/add-a-skill.sh research/pricing-workshop-notes.md
./scripts/test-a-skill.sh --skill <new-skill-name> --smoke
python3 scripts/check-skill-metadata.py skills/<new-skill-name>/SKILL.md
```
Expected result:
- New skill folder exists
- Skill passes structural and metadata checks
- README catalog entry added/updated
### Anti-Pattern Example
"We wrote a cool skill, skipped validation, forgot README counts, and shipped anyway."
Result:
- Broken references
- Inconsistent catalog numbers
- Confusion for contributors and users
## Common Pitfalls
- Shipping vibes, not standards.
- Choosing `workflow` when the task is really a component template.
- Bloated descriptions that exceed upload limits.
- Descriptions that say what the skill is but not when Claude should trigger it.
- Descriptions that silently hit the 200-char limit and get cut off mid-thought.
- Letting `intent` become a substitute for a weak trigger description.
- Forgetting to update README counts after adding a skill.
- Treating generated output as final without review.
## References
- `README.md`
- `AGENTS.md`
- `CLAUDE.md`
- `docs/Building PM Skills.md`
- `docs/Add-a-Skill Utility Guide.md`
- Anthropic's [Complete Guide to Building Skills for Claude](https://resources.anthropic.com/hubfs/The-Complete-Guide-to-Building-Skill-for-Claude.pdf)
- `scripts/add-a-skill.sh`
- `scripts/build-a-skill.sh`
- `scripts/find-a-skill.sh`
- `scripts/test-a-skill.sh`
- `scripts/check-skill-metadata.py`
- `scripts/check-skill-triggers.py`
- `scripts/zip-a-skill.sh`
章节与文件索引
按说明文件中的顺序排列。
目的
狗粮优先
选择正确的创作路径
完成的定义(无例外)
促进真相来源
文件/命令 -> skills/<skill-name>/SKILL.md · scripts/find-a-skill.sh · scripts/add-a-skill.sh · scripts/build-a-skill.sh · scripts/test-a-skill.sh · scripts/check-skill-metadata.py · build-a-skill.sh · add-a-skill.sh
内容校验值 -> 108598482104
当前原文的自动摘译,尚未人工审校。
目的
轻松创建或更新 PM 技能。此工作流程将粗略的笔记、研讨会内容或半生不熟的提示转储转换为实际通过验证并属于此存储库的合规
skills/<skill-name>/SKILL.md资产。当您想要发布新技能而不需要“对我来说看起来不错”轮盘赌时,请使用它。狗粮优先
在发明自定义流程之前使用 repo-native 工具和标准:
scripts/find-a-skill.shscripts/add-a-skill.shscripts/build-a-skill.shscripts/test-a-skill.sh选择正确的创作路径
引导向导(
build-a-skill.sh):当你有一个想法但不是最终的散文时最好。内容优先生成器(add-a-skill.sh):当您已经拥有源内容时最好。手动编辑+验证:最适合加强现有技能。完成的定义(无例外)
仅当满足以下条件时才完成技能: Frontmatter 有效(
name、description、intent、type) 章节顺序合规 遵守元数据限制(name<= 64 个字符、description<= 200 个字符) 说明说明了该技能的作用以及何时使用该技能促进真相来源
当将此工作流程作为引导对话运行时,请使用
workshop-facilitation作为交互协议。它定义: 会话提示 + 输入模式(引导、上下文转储、最佳猜测) 带有简单语言提示的单问题轮流 进度标签(例如,上下文 Qx/8 和评分 Qx/5)