agentsclimarketplace
Sign in

Rewrite descriptions

Skill theagenticguy/agentic-plugins/plugins/plugin-gardener/skills/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.From its SKILL.md

Install
npx -y skills add theagenticguy/agentic-plugins --skill rewrite-descriptions

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
  • runs commandsInstructs the agent to run 1 command, including `/audit-skill <name>`.

SKILL.md

2.8 KB, 450 tokens by cl100k_base, as published. Nobody here has run it

Contents

ReferenceWhen to load
../../references/write-protocol.mdWrite discipline for the proposal file
references/rewriting-patterns.mdPatterns specific to description fixes
templates/proposal-skeleton.mdOutput 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

  1. 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.

What ships with it: 2 files

5.0 KB alongside SKILL.md

references/

templates/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.