rules-eval

# Rules Evaluation Framework ## When NOT To Use - Evaluating skills (use `abstract:skills-eval`) - Evaluating hooks (use `abstract:hooks-eval`) - Writing a new rule (use `hookify:writing-rules`) ## Table of Contents 1. [Overview](#overview) 2. [Quick Start](#quick-start) 3. [Evaluation Workflow](#evaluation-workflow) 4. [Scoring](#scoring) 5. [Resources](#resources) ## Overview 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. ## Quick Start ```bash # Evaluate rules in current project /rules-eval # Evaluate specific directory /rules-eval .claude/rules/ # Detailed analysis with recommendations /rules-eval --detailed ``` ## Evaluation Workflow 1. Scan `.claude/rules/` for all `.md` files (including subdirectories) 2. Validate YAML frontmatter syntax and fields 3. Analyze glob patterns for correctness and specificity 4. Assess content quality (actionable, concise, non-conflicting) 5. Check organization (naming, structure, symlinks) 6. Measure token efficiency and redundancy ## Scoring | Category | Points | Focus | |----------|-----...