plugins/abstract/skills/rules-eval/SKILL.md
Evaluate Claude Code rules in .claude/rules/. Use for frontmatter, globs, and quality audits.
npx skillsauth add athola/claude-night-market rules-evalInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill evaluates Claude Code rules in .claude/rules/ directories against quality standards. It validates YAML frontmatter, glob pattern syntax, content quality, and directory organization. Rules files support path-scoped conditional loading via paths frontmatter and unconditional rules (no paths field).
Key validations: YAML syntax errors, unquoted glob patterns, Cursor-specific fields (alwaysApply, globs), overly broad patterns, content verbosity, and naming conventions.
# Evaluate rules in current project
/rules-eval
# Evaluate specific directory
/rules-eval .claude/rules/
# Detailed analysis with recommendations
/rules-eval --detailed
.claude/rules/ for all .md files (including subdirectories)| Category | Points | Focus | |----------|--------|-------| | Frontmatter Validity | 25 | YAML syntax, required fields, correct field names | | Glob Pattern Quality | 20 | Syntax, specificity, quoting | | Content Quality | 25 | Actionable, concise, non-conflicting | | Organization | 15 | Naming, structure, symlink usage | | Token Efficiency | 15 | Rule size, redundancy detection |
| Score | Level | |-------|-------| | 91-100 | Excellent - Production-ready | | 76-90 | Good - Minor improvements possible | | 51-75 | Basic - Needs optimization | | 26-50 | Below Standards - Significant issues | | 0-25 | Critical - Invalid or broken rules |
modules/frontmatter-validation.mdmodules/glob-pattern-analysis.mdmodules/content-quality-metrics.mdmodules/organization-patterns.mdscripts/rules_validator.pyabstract:skills-eval - Skill evaluation frameworkabstract:hooks-eval - Hook evaluation frameworktools
Detect friction signals; graduate patterns into rules. Use for session retrospectives.
testing
Use when you need a diff-derived test plan for an MR — reads the diff, groups changes by area, runs targeted verifications, and proves revert-tests are genuine guards, not dead assertions.
development
Curate the web-capture index. Use when the capture backlog grows, captures sit unprocessed at seedling/pending, or to surface stored research during work.
testing
Probe memory/summary clarity via dual anchor questions: task progress, info gaps. Use when verifying session state or summary before handoff or compression.