rules-eval
Evaluate and validate Claude Code rules in .claude/rules/ directories. Use when auditing rule file quality, validating frontmatter and glob patterns, or checking rules organization before deployment. Do not use when writing new rules from scratch - use rule authoring guides instead. Do not use when evaluating skills or hooks - use skills-eval or hooks-eval instead.
Best use case
rules-eval is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Evaluate and validate Claude Code rules in .claude/rules/ directories. Use when auditing rule file quality, validating frontmatter and glob patterns, or checking rules organization before deployment. Do not use when writing new rules from scratch - use rule authoring guides instead. Do not use when evaluating skills or hooks - use skills-eval or hooks-eval instead.
Teams using rules-eval should expect a more consistent output, faster repeated execution, less prompt rewriting, better workflow continuity with your supporting tools.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
- You already have the supporting tools or dependencies needed by this skill.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/rules-eval/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How rules-eval Compares
| Feature / Agent | rules-eval | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Evaluate and validate Claude Code rules in .claude/rules/ directories. Use when auditing rule file quality, validating frontmatter and glob patterns, or checking rules organization before deployment. Do not use when writing new rules from scratch - use rule authoring guides instead. Do not use when evaluating skills or hooks - use skills-eval or hooks-eval instead.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Rules Evaluation Framework ## 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 | |----------|--------|-------| | 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 | ## Resources ### Skill-Specific Modules - **Frontmatter Validation**: See `modules/frontmatter-validation.md` - **Glob Pattern Analysis**: See `modules/glob-pattern-analysis.md` - **Content Quality Metrics**: See `modules/content-quality-metrics.md` - **Organization Patterns**: See `modules/organization-patterns.md` ### Tools - **Rules Validator**: `scripts/rules_validator.py` ### Related Skills - `abstract:skills-eval` - Skill evaluation framework - `abstract:hooks-eval` - Hook evaluation framework
Related Skills
skills-eval
Evaluate and improve Claude skill quality through auditing
technical-accuracy-and-usability-rules
Ensures the documentation is technically accurate and highly usable for the target audience.
tech-stack-evaluator
Auto-activates during requirements analysis to evaluate technical stack compatibility, recommend appropriate technologies, and assess performance implications.
rules-migration
MIGRATE CLAUDE.md into modular `.claude/rules/` directory structure following Claude Code's rules system. Converts monolithic CLAUDE.md into organized, path-specific rule files with glob patterns. Use when migrating to rules system, modularizing project instructions, splitting CLAUDE.md, organizing memory files. Triggers on "migrate claudemd to rules", "convert claude.md to rules", "modularize claude.md", "split claude.md into rules", "migrate to rules system".
python-fastapi-scalable-api-cursorrules-prompt-fil-cursorrules
Apply for python-fastapi-scalable-api-cursorrules-prompt-fil. --- description: Applies general coding style and structure rules for Python code in the backend. globs: backend/src/**/*.py
prompt-generation-rules
General rules to generate prompt.
packaging-rules
BrainDrive plugin packaging and ZIP rules - use when creating the final distributable package or validating ZIP structure
my-react-rules
This is a new rule
mobile-first-design-rules
Focuses on rules and best practices for mobile-first design and responsive typography using tailwind.
mcp-server-evaluations
Test MCP servers for quality and reliability. Verify tool functionality, test error handling, generate tests, and assess response quality with no dependencies other than curl. Use this when validating MCP server implementations, testing OpenAPI-to-MCP conversions, or assessing API tool quality.
history-and-next-task-rules
Specifies the format for ending responses, including a summary of requirements, code written, source tree, and next task, applying to all files.
get-qodo-rules
Loads org- and repo-level coding rules from Qodo before code tasks begin, ensuring all generation and modification follows team standards. Use before any code generation or modification task when rules are not already loaded. Invoke when user asks to write, edit, refactor, or review code, or when starting implementation planning.