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.3 KiB
1.3 KiB
Fix Skills
When a skill or its scripts fail to produce expected results, or throw errors.
See
{baseDir}/docs/standard.mdfor skill structure and layer responsibilities.
Principle
Do not resort to workarounds lightly. Identify the root cause first, then fix properly.
Process
1. Gather Information
- Record the triggering scenario: how it was called, expected result, actual result
- Record the error output in full (stack traces, debug output)
- Confirm the environment: model version, node, skill version (git log helps)
2. Analyze Root Cause
Investigate in this order:
- Are inputs/parameters correct? — Do they match what the script expects?
- Are dependencies satisfied? — Required secrets, tokens, config files present?
- Is there a bug in the script logic? — Read the source, add
set -xif needed - 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 workflow
- If it's an environment issue → document in memory/
4. Fix
- Test the fix locally
- 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