Audit skill
Skill theagenticguy/agentic-plugins/plugins/plugin-gardener/skills/audit-skill
Public Claude Code plugin marketplace — installable skills and agents for AI coding agents. Drop-in capabilities you add with one command.
npx -y skills add theagenticguy/agentic-plugins --skill audit-skillAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing 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.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
3.1 KB, as published. Nobody here has run it
Contents
| Reference | When to load |
|---|---|
../../references/rubric.md | The scoring rubric (shared) |
../../references/write-protocol.md | Write discipline |
templates/scorecard-skeleton.md | Output file shape |
Audit a skill
Score one skill against the 7-dimension rubric. The skill is the input; a scorecard Markdown file is the output.
How it works
- Resolve
{{ skill }}to an absolute path. Accept either a directory path (skills/research) or a bare skill name (research) — glob for the matchingSKILL.md. - Read the rubric at
${CLAUDE_PLUGIN_ROOT}/references/rubric.md. - Read the skill in full: SKILL.md, every file under
references/, every file undertemplates/. The scorecard is grounded in what's in the files, not in the description alone. Reading is the primary work. - If a prior
/gardeneraudit exists atplugin-gardener/audit/, read its latestcollisions.csvandclusters.csvfor 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. - Write a scorecard to
plugin-gardener/audit/ad-hoc/<skill-name>-<YYYY-MM-DD>.mdusingtemplates/scorecard-skeleton.md. - Present the total, dimension scores, and top-3 recommended actions inline.
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.
When to invoke
- After authoring a new skill — baseline the score before committing.
- After a monthly
/gardenerrun flags a skill — re-score to confirm the issue. - After applying fixes — did the score improve?
What this does not do
- Edit the skill.
- Open a PR.
- Change frontmatter.
The scorecard is the deliverable. Changes are the user's to apply.