How do I install the Rewrite Descriptions skill?

Run npx skillmds@latest add theagenticguy/rewrite-descriptions in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Rewrite Descriptions safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Rewrite Descriptions?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Rewrite Descriptions free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Rewrite Descriptions?

theagenticguy (@theagenticguy) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Rewrite Descriptions by theagenticguy

Name: Rewrite Descriptions
Author: theagenticguy

Rewrite Descriptions

Propose description rewrites to resolve skill collisions. Given a collision pair from a gardener audit, reads both skills' descriptions, generates before/after rewrites with negative discriminators, and writes a proposal Markdown the user applies manually. Uses current Claude prompting discipline: positive imperatives, motivation clauses, scope explicit. Use when the user asks to fix a collision, rewrite a description, disambiguate two skills, or mentions resolving a gardener-flagged pair.

theagenticguy 999c1f8 3 files · 7.6 KB Updated Sep 17, 2026

File contents

Reference	When to load
`../../references/write-protocol.md`	Write discipline for the proposal file
`references/rewriting-patterns.md`	Patterns specific to description fixes
`templates/proposal-skeleton.md`	Output file shape

Rewrite descriptions

Given a collision pair, produce a concrete description rewrite proposal for each side. The output is a Markdown file with before/after blocks the user copies into the SKILL.md files manually.

Inputs

{{ pair }} — either skill-a,skill-b or a single skill name. If single, read plugin-gardener/audit/ for the latest collisions.md and pick the top unresolved collision involving that skill.

How it works

Resolve each skill path. Read both SKILL.md files and capture the current description + optional when_to_use.
Apply the rewriting patterns in references/rewriting-patterns.md. Every rewrite must:
- Keep each description under 1,024 characters (hard Anthropic cap).
- Combined description + when_to_use under 1,536 characters (skill listing cap).
- Add a negative discriminator on each side that points at the other: Do NOT use when the user mentions [sibling-domain-term].
- Use third-person voice, positive imperatives, one motivation clause where non-obvious.
- Preserve the Use when the user asks to … clause structure if it was already there.
Write plugin-gardener/audit/ad-hoc/rewrite-<skill-a>-vs-<skill-b>-<YYYY-MM-DD>.md using templates/proposal-skeleton.md.
Present the proposal inline so the user can copy-paste without opening the file.

What this does not do

Edit SKILL.md.
Commit changes.
Regenerate SKILL.md bodies. Description-only changes; the skill content is untouched.

The user applies the rewrite manually. After applying, invoke /audit-skill <name> on both sides to confirm the collision is resolved.

---name: rewrite-descriptionsdescription: Propose description rewrites to resolve skill collisions. Given a collision pair from a gardener audit, reads both skills' descriptions, generates before/after rewrites with negative discriminators, and writes a proposal Markdown the user applies manually. Uses current Claude prompting discipline: positive imperatives, motivation clauses, scope explicit. Use when the user asks to fix a collision, rewrite a description, disambiguate two skills, or mentions resolving a gardener-flagged pair.---## Contents| Reference | When to load || ------------------------------------ | -------------------------------------- || `../../references/write-protocol.md` | Write discipline for the proposal file || `references/rewriting-patterns.md` | Patterns specific to description fixes || `templates/proposal-skeleton.md` | Output file shape |# Rewrite descriptionsGiven a collision pair, produce a concrete description rewrite proposal for each side. The output is a Markdown file with before/after blocks the user copies into the SKILL.md files manually.## Inputs- `{{ pair }}` — either `skill-a,skill-b` or a single skill name. If single, read `plugin-gardener/audit/` for the latest `collisions.md` and pick the top unresolved collision involving that skill.## How it works1. Resolve each skill path. Read both SKILL.md files and capture the current `description` + optional `when_to_use`.2. Apply the rewriting patterns in `references/rewriting-patterns.md`. Every rewrite must: - Keep each description under 1,024 characters (hard Anthropic cap). - Combined `description + when_to_use` under 1,536 characters (skill listing cap). - Add a negative discriminator on each side that points at the other: `Do NOT use when the user mentions [sibling-domain-term]`. - Use third-person voice, positive imperatives, one motivation clause where non-obvious. - Preserve the `Use when the user asks to …` clause structure if it was already there.3. Write `plugin-gardener/audit/ad-hoc/rewrite-<skill-a>-vs-<skill-b>-<YYYY-MM-DD>.md` using `templates/proposal-skeleton.md`.4. Present the proposal inline so the user can copy-paste without opening the file.## What this does not do- Edit SKILL.md.- Commit changes.- Regenerate SKILL.md bodies. Description-only changes; the skill content is untouched.The user applies the rewrite manually. After applying, invoke `/audit-skill <name>` on both sides to confirm the collision is resolved.

Frequently asked questions