1.5 KiB
1.5 KiB
name, description
| name | description |
|---|---|
| skill-rewriter | Rewrite an existing Agent Skill into a concise, safer, and more discoverable package while preserving its intended capability. Use after a skill review or when the user asks to improve a SKILL.md; do not alter original submissions in place without explicit approval. |
Skill rewriter
Create a separate revised package so the author can compare it with the original. Retain domain-specific facts that are supported by the source; replace generic filler with decisions the agent would otherwise miss.
Rewrite flow
- Read the original package and any review brief. Keep its intended job and remove only unsupported assumptions, unsafe commands, or instructions that conflict with the requested boundary.
- Write valid frontmatter: a lowercase hyphenated name matching the folder and a description that states capability plus trigger terms.
- Use a short, friendly structure: Purpose, When to use, Inputs, Workflow, Rules, Output, and Verification. Omit headings that add no decision-making value.
- Move conditional detail to
references/; add a script only for deterministic repeated work and name its prerequisites. Use paths relative to the skill root. - Add concrete safety gates for mutation, credentials, and external systems. Never preserve a secret in the rewritten package.
- Validate the new package and give the author an end-to-end explanation of the changes and one next evaluation step.
Read the rewrite checklist for final checks.