Heal a Skill
Repair the invoked skill and its supporting resources from concrete failure evidence or current authoritative documentation.
Runtime and Path Resolution
Use the invoked skill path supplied by the active skill catalog or loader. If it is unavailable, search the configured skill roots and the current repository for an exact name: match. Never assume the current directory contains ./skills/<name>. Use the user's current message and conversation context as inputs; do not depend on harness-specific variables.
For questions, progress tracking, delegation, or related skills, use the active runtime equivalents in RUNTIME_TOOLS.md when available, with a plain-language fallback when a mapped capability is absent.
Workflow
- Read the target
SKILL.md fully, then inspect only the related references, scripts, metadata, and callers needed to understand the failure.
- State the observed failure, the incorrect instruction, the root cause, affected files, and the proposed correction. Use exact errors and current primary sources where an external contract is involved.
- Preserve authorization already given. If the user explicitly asked to fix or heal the skill, proceed with in-scope edits without requesting approval again. Ask only when the target is ambiguous, the proposed change conflicts with the user's direction, or a separate external action such as publishing or pushing lacks authorization.
- Make the smallest complete correction. Update all examples and supporting resources that encode the same wrong behavior.
- Read back the changed sections, run the skill validator when available, and perform a focused behavioral check for scripts or fragile commands.
- Report changed files, verification, and any remaining uncertainty. Commit only when the user has authorized a commit.
Success Criteria
- The exact loaded skill was repaired.
- The correction is supported by failure evidence, repository behavior, or current primary documentation.
- Related examples and references agree with the entrypoint.
- No unrelated files or external systems were changed.
1---2name: heal-skill3description: Correct a skill whose instructions, paths, commands, or external API guidance were shown to be wrong or stale.4---56# Heal a Skill78Repair the invoked skill and its supporting resources from concrete failure evidence or current authoritative documentation.910## Runtime and Path Resolution1112Use the invoked skill path supplied by the active skill catalog or loader. If it is unavailable, search the configured skill roots and the current repository for an exact `name:` match. Never assume the current directory contains `./skills/<name>`. Use the user's current message and conversation context as inputs; do not depend on harness-specific variables.1314For questions, progress tracking, delegation, or related skills, use the active runtime equivalents in [RUNTIME_TOOLS.md](../RUNTIME_TOOLS.md) when available, with a plain-language fallback when a mapped capability is absent.1516## Workflow17181. Read the target `SKILL.md` fully, then inspect only the related references, scripts, metadata, and callers needed to understand the failure.192. State the observed failure, the incorrect instruction, the root cause, affected files, and the proposed correction. Use exact errors and current primary sources where an external contract is involved.203. Preserve authorization already given. If the user explicitly asked to fix or heal the skill, proceed with in-scope edits without requesting approval again. Ask only when the target is ambiguous, the proposed change conflicts with the user's direction, or a separate external action such as publishing or pushing lacks authorization.214. Make the smallest complete correction. Update all examples and supporting resources that encode the same wrong behavior.225. Read back the changed sections, run the skill validator when available, and perform a focused behavioral check for scripts or fragile commands.236. Report changed files, verification, and any remaining uncertainty. Commit only when the user has authorized a commit.2425## Success Criteria2627- The exact loaded skill was repaired.28- The correction is supported by failure evidence, repository behavior, or current primary documentation.29- Related examples and references agree with the entrypoint.30- No unrelated files or external systems were changed.
SomtoUgeh