- skill-audit: promote internal-working gotcha to ## Gotchas section; narrow cross-plugin path check to exclude tests/ (dev-only, repo-level deps are expected); require tests/README.md to declare that dependency - skill-write/skill-improve: reorder descriptions to lead with "Use when..." for consistency with skill-audit and the agentskills.io spec trigger pattern - skill-write: add tests/README.md with self-contained bats setup instructions; remove cross-skill reference to skill-audit's tests/README.md 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 |