Help us improve
Share bugs, ideas, or general feedback.
From plugin-gardener
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.
npx claudepluginhub theagenticguy/agentic-plugins --plugin plugin-gardenerHow this skill is triggered — by the user, by Claude, or both
Slash command
/plugin-gardener:rewrite-descriptionsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
| Reference | When to load |
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Implements vector databases with Pinecone, Weaviate, Qdrant, Milvus, pgvector for semantic search, RAG, recommendations, and similarity systems. Optimizes embeddings, indexing, and hybrid search.
Share bugs, ideas, or general feedback.
| 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 |
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.
{{ 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.description + optional when_to_use.references/rewriting-patterns.md. Every rewrite must:
description + when_to_use under 1,536 characters (skill listing cap).Do NOT use when the user mentions [sibling-domain-term].Use when the user asks to … clause structure if it was already there.plugin-gardener/audit/ad-hoc/rewrite-<skill-a>-vs-<skill-b>-<YYYY-MM-DD>.md using templates/proposal-skeleton.md.The user applies the rewrite manually. After applying, invoke /audit-skill <name> on both sides to confirm the collision is resolved.