rule-effectiveness
Analyze which rules are actively used vs inert. Detect coverage gaps. Recommend pruning to reduce token consumption.
npx skills add majiayu000/claude-skill-registry --skill rule-effectiveness --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Rule Effectiveness Analysis Analyze the effectiveness of `.claude/rules/` in the current project by cross-referencing rule globs against actual file activity from git history. ## Step 1: Collect rules inventory Read all `.md` files in `.claude/rules/`. For each: 1. Extract `globs:` value from YAML frontmatter 2. Count lines of content (excluding frontmatter) 3. Record filename and glob pattern If a rule has no `globs:` or `paths:` frontmatter, classify as **always-loaded** (loads every session regardless of files touched). Rules with `globs:` load eagerly at session start. Rules with `paths:` + `alwaysApply: false` load lazily (only when a matching file is touched). Note: `paths:` must be unquoted CSV — YAML arrays and quoted strings fail silently. ## Step 2: Collect file activity from git history Run: `git log --name-only --pretty=format:'' --since='3 months ago'` (or configurable period). Parse output to build: - **session_files**: group files by commit date (approximate 1 day = 1 session) - **total_sessions**: count distinct dates with commits - **all_files_touched**: unique set of all files modified If fewer than 5 sessions available, warn that results may not be representati
- Step 1: Collect rules inventory
- Step 2: Collect file activity from git history
- Step 3: Cross-reference rules vs activity
- Step 4: Classify rules
- Step 5: Detect coverage gaps
- Step 6: Token optimization analysis
- Step 7: Generate report
- Step 8: Offer automated fixes
What does the rule-effectiveness skill do?
Analyze which rules are actively used vs inert. Detect coverage gaps. Recommend pruning to reduce token consumption.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill rule-effectiveness --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.