CtrlK
BlogDocsLog inGet started
Tessl Logo

rules-auditor

Audit Claude Code rules and CLAUDE.md/AGENTS.md files for staleness, quality, and drift. Use when asked to audit rules, check stale CLAUDE.md, check stale AGENTS.md, review rules freshness, assess rules quality, improve my rules, find dead globs in rules, check if rules are up to date, review progressive disclosure setup, find contradictory rules, or optimize Claude Code memory files.

72

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured, actionable skill with clear multi-step workflows and concrete bash commands for each audit phase. Its main weakness is moderate verbosity from repeated explanations (especially about AGENTS.md equivalence) and some content that could be offloaded to reference files. The progressive disclosure structure is well-signaled but cannot be fully verified without bundle files.

Suggestions

Remove the repeated explanation that AGENTS.md is identical to CLAUDE.md — state it once in the Overview and trust Claude to apply it throughout.

Consider moving the detailed audit steps (Steps 3-5 especially) into a reference file to keep SKILL.md as a concise overview with the discovery workflow and high-level audit checklist.

DimensionReasoningScore

Conciseness

Generally efficient but has some redundancy — the explanation that AGENTS.md is identical to CLAUDE.md is repeated three times (overview, discovery step 2 note, and implicitly throughout). Some sections like the freshness scoring table and structural verification could be tighter. However, it mostly avoids explaining things Claude already knows.

2 / 3

Actionability

Provides concrete, executable bash commands for every discovery and audit step — glob testing, frontmatter extraction, file reference verification, and dead glob detection. The commands are copy-paste ready and specific to the task.

3 / 3

Workflow Clarity

The workflow is clearly sequenced in two phases (Discovery 1-4, then Audit Steps 1-7) with explicit validation at each step. Each step has clear pass/fail criteria (e.g., dead globs, broken refs, <50% convention adherence) and the freshness scoring table provides a structured evaluation framework. The report generation step serves as a final validation checkpoint.

3 / 3

Progressive Disclosure

The Reference Navigation table clearly signals four reference files with one-level-deep links, which is good structure. However, since no bundle files were provided, we cannot verify these references exist. Additionally, the main SKILL.md itself is fairly long (~120 lines of content) and some of the detailed audit steps (like convention drift detection) could potentially be offloaded to reference files to keep the overview leaner.

2 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that clearly defines a specific niche (auditing Claude Code rules and memory files), lists concrete actions, and provides comprehensive trigger terms in an explicit 'Use when...' clause. It covers both what the skill does and when to use it with natural language triggers that users would actually say. The description is well-structured, distinctive, and unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: audit rules, check staleness, assess quality, detect drift, find dead globs, find contradictory rules, review progressive disclosure setup, and optimize memory files.

3 / 3

Completeness

Clearly answers both 'what' (audit Claude Code rules and CLAUDE.md/AGENTS.md files for staleness, quality, and drift) and 'when' (explicit 'Use when...' clause with extensive list of trigger scenarios).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'audit rules', 'stale CLAUDE.md', 'stale AGENTS.md', 'rules freshness', 'rules quality', 'improve my rules', 'dead globs', 'rules up to date', 'contradictory rules', 'Claude Code memory files'. These are highly natural phrases a user would use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive niche focused specifically on auditing Claude Code rules and configuration files. The specific mentions of CLAUDE.md, AGENTS.md, dead globs, progressive disclosure, and rules staleness make it very unlikely to conflict with other skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
seanGSISG/claude-depot
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.