Use when a skill isn't triggering as expected, before adding a new skill (to check for a name collision), during periodic cleanup of an accumulated skills directory, or when asked to review skill quality — checks frontmatter validity, description quality against Skill Discovery Optimization conventions, body size, and cross-scope name collisions.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Skill Audit
## Overview
Skills accumulate. Nobody deletes them, most developers hit 8-12 installed skills before the per-session token cost of loading every description starts to outweigh the benefit, and a skill installed at both the personal and project scope with the same name fails silently — the higher-precedence one wins and the other never fires, with no error anywhere. This script checks the mechanical properties that predict a skill working or silently failing: valid frontmatter, a description that leads with the trigger (not a workflow summary), a body under the token-efficiency guideline, and no name collision across scopes.
**Core principle:** A skill that never triggers and a skill that doesn't exist have the same effect on the user, but only one of them is visible in a directory listing. This script finds the invisible kind.
## Usage
```bash
python3 ${CLAUDE_SKILL_DIR}/scripts/audit.py [skills_dir ...]
```
…
The line at the top of this page pins the label git:20260904.a4fa3d2, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_tcmxhldu3pnox6ka
GET https://markdownregistry.com/api/v1/resolve?ref=rtur2003/claude-code-promts-skills/skill-audit
GET https://markdownregistry.com/api/v1/blob/e7a5d6f15b068732876ba6d6b444f5fd21236b62b85e6ce0275d05694e405037
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
rtur2003/claude-code-promts-skills · .agents/skills/capability-audit/SKILL.md · Use when evaluating, comparing, installing, or recommending a Claude Code plugin, Agent Skill, MCP server, agent…
rtur2003/claude-code-promts-skills · .agents/skills/changelog-from-commits/SKILL.md · Use when cutting a release, writing a CHANGELOG entry, or summarizing what changed since a tag — when the repo's…
rtur2003/claude-code-promts-skills · .agents/skills/deterministic-checks/SKILL.md · Use before committing, opening a PR, or reporting a task done — when you want ground-truth confirmation there are no…
rtur2003/claude-code-promts-skills · .agents/skills/doc-link-audit/SKILL.md · Use before publishing documentation, merging a docs PR, or reporting a Markdown-heavy repo's navigation as complete —…
rtur2003/claude-code-promts-skills · .agents/skills/find-prompt/SKILL.md · Use when the user names a coding, Claude Code, research, documentation, or technology-selection task; asks which prompt…
rtur2003/claude-code-promts-skills · .agents/skills/skill-audit/SKILL.md · Use when a skill isn't triggering as expected, before adding a new skill (to check for a name collision), during…
rtur2003/claude-code-promts-skills · .claude/skills/capability-audit/SKILL.md · Use when evaluating, comparing, installing, or recommending a Claude Code plugin, Agent Skill, MCP server, agent…
rtur2003/claude-code-promts-skills · .claude/skills/changelog-from-commits/SKILL.md · Use when cutting a release, writing a CHANGELOG entry, or summarizing what changed since a tag — when the repo's…
rtur2003/claude-code-promts-skills · .claude/skills/deterministic-checks/SKILL.md · Use before committing, opening a PR, or reporting a task done — when you want ground-truth confirmation there are no…
rtur2003/claude-code-promts-skills · .claude/skills/doc-link-audit/SKILL.md · Use before publishing documentation, merging a docs PR, or reporting a Markdown-heavy repo's navigation as complete —…
rtur2003/claude-code-promts-skills · .claude/skills/find-prompt/SKILL.md · Use when the user names a coding or Claude Code task ("add OAuth", "set up hooks", "review this PR", "pick a model")…
nyldn/claude-octopus · .claude/skills/skill-audit/SKILL.md · Audit codebases for quality, consistency, and broken patterns — use for pre-release or tech debt review
nyldn/claude-octopus · skills/skill-audit/SKILL.md · Audit codebases for quality, consistency, and broken patterns — use for pre-release or tech debt review
majiayu000/spellbook · skills/skill-audit/SKILL.md · Audit, design, categorize, distribute, and measure agent skills using lessons from Anthropic's Lessons from building…
bug-ops/zeph · .zeph/skills/skill-audit/SKILL.md · Audit installed skills for agentskills.io specification compliance and security issues. Use when the user asks to…
rtur2003/claude-code-promts-skills · .agents/skills/skill-audit/SKILL.md · Use when a skill isn't triggering as expected, before adding a new skill (to check for a name collision), during…
vanducng/skills · skills/skill-audit/SKILL.md · Mine your Claude Code, Codex, pi and Cursor session history for how your skills actually get used - invocations…
