From abstract
Evaluates Claude Code rules in .claude/rules/ for frontmatter validity, glob pattern quality, content quality, organization, and token efficiency.
How this skill is triggered — by the user, by Claude, or both
Slash command
/abstract:rules-evalThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Evaluating skills (use `abstract:skills-eval`)
abstract:skills-eval)abstract:hooks-eval)hookify:writing-rules)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 framework.md file under .claude/rules/ (including subdirectories) receives a quality score
(0-100) with per-category breakdown across the five dimensions.alwaysApply, globs) are flagged as
non-compliant with the expected Claude Code schema.npx claudepluginhub athola/claude-night-market --plugin abstractGuides authoring .claude/rules/*.md files for auto-applied, file-pattern-scoped constraints on code conventions, quality standards, and project-specific guidance.
Guides writing effective .claude/rules/ files for Claude Code, with imperative framing and enforceability checks. Useful when creating or refining project-specific rules.
Inspect and maintain the live-rules in the project's live-rules file (.claude/live-rules.md by default, or wherever LIVE_RULES_PATH points): list every rule with its scope and status, audit them for problems (broken frontmatter, globs that match nothing, duplicates, oversized bodies, conflicts), enable or disable a rule, or explain which rules are currently active. Use when the user asks to "list my rules", "what rules are active", "show live-rules", "audit my rules", "disable the X rule", "enable the X rule", "turn off that rule", "why did Claude get that instruction", or "clean up my rules". To create or edit a rule, use add-rule instead.