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

21
claw-skills/workflows/fix-skills.md
View File

@@ -1,13 +1,13 @@
# fix-skills
# Fix Skills
Used when a skill or its scripts fail to produce expected results, or throw errors.
When a skill or its scripts fail to produce expected results, or throw errors.
> See `{baseDir}/docs/standard.md` for skill structure and layer responsibilities.
## Principle
**Do not resort to workarounds lightly.** Identify the root cause first, then fix properly.
> See `{baseDir}/docs/standard.md` for skill structure and writing requirements.
## Process
### 1. Gather Information
@@ -20,24 +20,23 @@ Used when a skill or its scripts fail to produce expected results, or throw erro
Investigate in this order:
1. **Are inputs/parameters correct?** — Do they match what the script or tool expects?
2. **Are dependencies satisfied?** — Are required secrets, tokens, config files present?
1. **Are inputs/parameters correct?** — Do they match what the script expects?
2. **Are dependencies satisfied?** — Required secrets, tokens, config files present?
3. **Is there a bug in the script logic?** — Read the source, add `set -x` if needed
4. **Is there a design flaw in the skill?** — Does the logic actually cover this scenario?
4. **Is there a design flaw?** — Does the logic actually cover this scenario?
### 3. Pinpoint the File
- Identify which file and which line the problem is in
- If it's a skill issue → follow the [improve-skills](./improve-skills.md) workflow
- If it's an execution environment issue → document in memory/
- If it's a skill issue → follow the improve-skills workflow
- If it's an environment issue → document in memory/
### 4. Fix
- Test the fix locally
- If skill files need to be modified → follow improve-skills process to PR or push to a branch
- If skill files need modification → follow improve-skills process
- Avoid introducing new side effects
### 5. Verify
- Reproduce the original scenario; confirm the issue is resolved
- Log the fix in memory/YYYY-MM-DD.md