zhi
795a710376
Rewrote docs/standard.md as the single source of truth for skill structure (menu/tools/recipes/manual analogy). Trimmed all SKILL.md files to pure routers, moved recruitment workflow out of SKILL.md into workflows/recruitment.md, removed duplicated standards from workflow files. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1.4 KiB
1.4 KiB
Create Skills
When you notice a reusable pattern with no existing skill covering it.
See
{baseDir}/docs/standard.mdfor skill structure and layer responsibilities.
Principle
Not every repetitive task needs a skill. Ask first: is this pattern general enough to warrant abstraction?
Process
1. Identify the Pattern
- Record the repeating sequence of operations
- Analyze: what are you doing repeatedly across tasks?
- Evaluate: is this general-purpose or a one-off?
2. Decide the Approach
Should this be a new skill, or a script/workflow added to an existing skill?
Add a script when:
- The steps are fixed and results are predictable
- The operation recurs across different agents/workspaces
- Involves external system calls (git, keycloak, file ops, etc.)
Add a workflow when:
- Steps vary depending on context or require judgment
- The scenario is too nuanced for rigid logic
Not worth abstracting:
- One-off tasks
3. Design
- Name: kebab-case (e.g.,
git-clone-repo) - SKILL.md: Router only — list scripts with invocation syntax, workflows with trigger conditions
- Scripts: Single responsibility each, placed under
scripts/
4. Implement
- Write the scripts, verify they work
- Write the SKILL.md
- Test locally
5. Submit
Call {baseDir}/scripts/promote-improvements to push to your branch.
Commit message includes: skill name, what it does, usage example.