skill-audit is agent-read markdown (skill) from rtur2003/claude-code-promts-skills: 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..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns 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 ...]
```
With no arguments, checks `.claude/skills/` (project) and `~/.claude/skills/` (personal) if they exist. Pass explicit paths to also check a plugin's `skills/` directory. Exit code 0 = clean, 1 = findings, 2 = usage error.
```bash
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
GET https://markdownregistry.com/api/v1/artifacts/art_ckfnsbpgbnyvvp6o
GET https://markdownregistry.com/api/v1/resolve?ref=rtur2003/claude-code-promts-skills/skill-audit
GET https://markdownregistry.com/api/v1/blob/6d5b879e9b6f2e9d575c4b8d57201ee2f86b65123eb3bc22c08530150cc739ed
Your agent 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 · .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")…
rtur2003/claude-code-promts-skills · .claude/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…
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 · .claude/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…
