mcpbeat

Rules Eval

athola/rules-eval

Evaluate Claude Code rules in .claude/rules/. Use for frontmatter, globs, and quality audits.

2k tokens
context cost
the whole folder, loaded on every use
5
files
instructions only
0
copies elsewhere
how many repositories repackaged it
324
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/athola/claude-night-market --skill rules-eval

The instruction itself

12 sections, as written by the author

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

  • Overview
  • Quick Start
  • Evaluation Workflow
  • Scoring
  • 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

# Evaluate rules in current project
/rules-eval

# Evaluate specific directory
/rules-eval .claude/rules/

# Detailed analysis with recommendations
/rules-eval --detailed

Evaluation Workflow

  • Scan .claude/rules/ for all .md files (including subdirectories)
  • Validate YAML frontmatter syntax and fields
  • Analyze glob patterns for correctness and specificity
  • Assess content quality (actionable, concise, non-conflicting)
  • Check organization (naming, structure, symlinks)
  • 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
  • abstract:skills-eval - Skill evaluation framework
  • abstract:hooks-eval - Hook evaluation framework

Exit Criteria

  • [ ] Every .md file under .claude/rules/ (including subdirectories) receives a quality score

(0-100) with per-category breakdown across the five dimensions.

  • [ ] YAML frontmatter syntax errors and unquoted glob patterns are listed as blocking findings

before any score is reported.

  • [ ] Rules using Cursor-specific fields (alwaysApply, globs) are flagged as

non-compliant with the expected Claude Code schema.

  • [ ] Any rule scoring below 26 (Critical tier) is reported with at least one concrete

corrective action, not just a score.

How to use it

Copy the folder

Take athola/rules-eval from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.