Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From plugin-gardener
Score a single skill against the gardener rubric. Reads the skill's SKILL.md, references/, and templates/, then writes a 7-dimension scorecard with per-criterion rationales and a recommended-actions list. Isolated counterpart to /gardener: same rubric, one item at a time. Use when the user asks to audit a skill, score a skill, check if a skill is healthy, or wants to re-score after making changes.
npx claudepluginhub theagenticguy/agentic-plugins --plugin plugin-gardenerHow this skill is triggered — by the user, by Claude, or both
Slash command
/plugin-gardener:audit-skillThe 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/rubric.md | The scoring rubric (shared) |
../../references/write-protocol.md | Write discipline |
templates/scorecard-skeleton.md | Output file shape |
Score one skill against the 7-dimension rubric. The skill is the input; a scorecard Markdown file is the output.
{{ skill }} to an absolute path. Accept either a directory path (skills/research) or a bare skill name (research) — glob for the matching SKILL.md.${CLAUDE_PLUGIN_ROOT}/references/rubric.md.references/, every file under templates/. The scorecard is grounded in what's in the files, not in the description alone. Reading is the primary work./gardener audit exists at plugin-gardener/audit/, read its latest collisions.csv and clusters.csv for cross-reference context. Collisions involving this skill inform Dimension 1 (description quality) and Dimension 5 (proactive-label discipline) — check whether the description carries the right negative-keyword discriminators. For every collision row, open the sibling SKILL.md and verify by reading, not from the cosine alone.plugin-gardener/audit/ad-hoc/<skill-name>-<YYYY-MM-DD>.md using templates/scorecard-skeleton.md.Apply the rubric dimension by dimension. Record a short rationale (1–2 sentences with a file:line citation from the files you read) for every criterion scoring under 3 points. The rationale is the value; the number is the aggregate.
On the role of embedding data: collisions and clusters from a prior /gardener run are binoculars, not the photograph. They point you at the right cross-references to open. Verify every flagged collision by reading both SKILL.md files — a high cosine is an invitation to investigate, not a verdict.
/gardener run flags a skill — re-score to confirm the issue.The scorecard is the deliverable. Changes are the user's to apply.