rewrite-descriptions

A skill that drafts clearer descriptions for two overlapping skills after a catalogue audit finds a collision. It reads both descriptions and writes a proposal for the user to apply manually.

In plain words
What is it for?
Use it when a gardener audit identifies a description collision or when one skill needs a clearer distinction from a related skill.
Why use it?
It helps users tell similar skills apart, reducing the chance that the wrong one is selected. The proposed wording adds boundaries and phrases that distinguish each skill.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/theagenticguy/agentic-plugins/rewrite-descriptions
Any agent
npx skills add theagenticguy/agentic-plugins --skill rewrite-descriptions
Clone the repo
git clone --depth 1 https://github.com/theagenticguy/agentic-plugins

Made for: Claude Code, Codex.

Per session 96 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 621 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00096 $0.00621
Opus 5 $0.00048 $0.00311
Sonnet 5 $0.00019 $0.00124
Haiku 4.5 $0.00010 $0.00062

Measured 2d ago against content hash dbfa6b29022e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

rewrite-descriptions scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/plugin-gardener/skills/rewrite-descriptions/SKILL.md · 54 lines

How it starts

The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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

  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.

Read the full file on GitHub · 54 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 54 lines · 96 tokens per session scan A dbfa6b29022e

Subscribe to this mod's changes

rewrite-descriptions is a skill published in the GitHub repository theagenticguy/agentic-plugins (5 stars, last pushed 21d ago), licensed MIT. It adds 96 tokens to every session and 621 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

genesis

Use this skill BEFORE drafting any agentic primitive module (skill, persona scoping file, scope-attached rule file, orchestrator workflow) or when refactoring an existing one. Activate whenever the task asks to design, restructure, or critique an agentic module across any agent harness (Claude Code, Copilot, Cursor…

danielmeppiel/genesis · 169 tokens

genesis-evals

Use this skill to run the genesis maintainer-side eval suite against a target model (default: claude-opus-4.7). Activate when validating a genesis PR, when changing the genesis catalogue (architectural-patterns, primitives, design-patterns, refactor-patterns, composition-substrate, pattern-tradeoffs, SKILL.md), or…

danielmeppiel/genesis · 195 tokens

agents

Guidance for AI coding agents working on the adeptability (adept) codebase. Humans: see README.md for usage and CONTRIBUTING.md for the contributor workflow.

itaywol/adeptability · 5 tokens

using-adept

Use the adept CLI to author AI skills once and render them into Claude Code, Cursor, Codex, Copilot, and OpenCode. Apply when installing/syncing skills, editing skill.yaml/SKILL.md, or touching .adeptability/.

itaywol/adeptability · 54 tokens

authoring-adept-agents

Write a good, portable adept agent (subagent): trigger-shaped description, one job per agent, generator/evaluator separation, explicit boundaries, restricted tools. Apply when creating or editing an agent file or running adept agent add.

itaywol/adeptability · 47 tokens

authoring-adept-loops

Compose a loop — a scheduled system that discovers work, hands it to agents, verifies with an independent evaluator, persists state, and reschedules itself. Apply when the user wants automation that runs on a timer, a triage/babysitter routine, or asks about adept loop add.

itaywol/adeptability · 60 tokens