- validate.sh: move FAIL lines and failure summary to stdout; stderr reserved for fatal script errors only (missing SKILL.md, bad args) - skill-audit SKILL.md: replace concrete plugins/kyberforge/skills/... example with abstract placeholder to fix meta-circularity - skill-write SKILL.md: rephrase placeholder section-heading instruction to remove embedded FILL IN: from a code span, clearing validator false positive - skill-improve SKILL.md: wrap Step 2 root-cause example in a text fence - skill-write assets/templates/README.md: update Files table to individual- file rows so skill-audit can verify per-file coverage Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
skill-improve
Apply evidence-based improvements to an existing skill using signals from the current session.
What it does
Takes an existing skill directory and one or more improvement signals — grill output, audit findings, eval failures, human feedback, or inline session context — and applies targeted edits to the skill files. Groups signals by root cause before editing to avoid per-symptom patching. Hands off to /skill-audit when done.
Before you start
Have at least one improvement signal ready: a grill session output, /skill-audit report, eval results, feedback.json, or inline feedback describing what went wrong. If you have no signals and want a blind review, use /skill-audit instead.
Usage
/skill-improve
Provide the skill directory path and any signal files in the conversation. The skill gathers signals from context — you don't need to paste them in a specific format.
Files
| File | Purpose |
|---|---|
SKILL.md |
Skill instructions for agents |
README.md |
Human-facing description of the skill and its files |