lyn/ClawSkills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: enforce layer responsibilities across all skills

Browse Source 
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>
This commit is contained in:
zhi
2026-04-17 20:40:16 +00:00
parent fd0f84d6b8
commit 795a710376
9 changed files with 238 additions and 301 deletions
Download Patch File Download Diff File Expand all files Collapse all files

58
claw-skills/workflows/create-skills.md
View File

@@ -1,30 +1,12 @@
# create-skills
# Create Skills
Used when you notice patterns or workflows that could improve efficiency but have no skill covering them.
When you notice a reusable pattern with no existing skill covering it.
> See `{baseDir}/docs/standard.md` for skill structure and layer responsibilities.
## Principle
Not every repetitive task needs to become a skill. Ask first: is this pattern general enough to warrant abstraction?
> See `{baseDir}/docs/standard.md` for skill structure and writing requirements.
## When to Add a Script vs a Workflow to a Skill
A skill can contain scripts, workflows, or both. When extending a skill, decide which type to add:
**Add a script when:**
- The steps are fixed, 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 — the process needs human judgment or situational decisions
- The scenario is too nuanced for rigid logic
**Not worth abstracting:**
- One-off task
> Conversational/analytical work *can* be worth a workflow — e.g., an interview flow (`recruitment/intviewer`) that guides through questions contextually is a valid workflow.
Not every repetitive task needs a skill. Ask first: is this pattern general enough to warrant abstraction?
## Process
@@ -32,23 +14,29 @@ A skill can contain scripts, workflows, or both. When extending a skill, decide
- Record the repeating sequence of operations
- Analyze: what are you doing repeatedly across tasks?
- Evaluate: is this operation general-purpose or a one-off special case?
- Evaluate: is this general-purpose or a one-off?
### 2. Decide the Approach
Based on the criteria above, determine whether this should be a new skill, or a script/workflow added to an existing skill.
Should this be a new skill, or a script/workflow added to an existing skill?
### 3. Design the 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.)
- **Name:** kebab-case (e.g., `git-clone-repo`, `keycloak-create-user`)
- **SKILL.md contents:**
- Description: what this skill does
- Use cases: when to use it
- Scripts: all related scripts and how to call them
- **Scripts:**
- Place under `scripts/`
- Each script has a single responsibility
- Provide `--help` or `-h` support
**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