ReddRadar
Agent skill
grading-claude-agents-md
Grades and improves CLAUDE.md (Claude Code) and AGENTS.md (Codex/OpenCode) configuration files. Use when asked to grade, score, evaluate, audit, review, improve, fix, optimize, or refactor agent config files. Triggers on 'grade my CLAUDE.md', 'score my AGENTS.md', 'is my CLAUDE.md too big', 'improve my agent config', 'fix my CLAUDE.md', 'optimize context usage', 'reduce tokens in CLAUDE.md', or 'audit my config files'. Automatically grades both files if present, generates improvement plan, and implements changes on approval.
Install this agent skill to your Project
npx add-skill https://github.com/SpillwaveSolutions/grading-claude-agents-md-agentic-skill/tree/main/skills/grading-claude-agents-md
SKILL.md
Grading CLAUDE.md and AGENTS.md
Grade agent configuration files, generate improvement plans, and implement fixes.
Workflow
┌─────────────────────────────────────────────────────────────┐
│ 1. GRADE 2. PLAN 3. IMPLEMENT │
│ ───────── ───────── ───────────── │
│ Auto-detect Show issues Apply fixes │
│ files → Score with fixes → on approval → │
│ against rubric prioritized verify result │
└─────────────────────────────────────────────────────────────┘
Quick Start
- Detect config files: Look for CLAUDE.md and/or AGENTS.md in project
- Grade each file: Apply rubric from references/rubric.md
- Generate report: Score card + prioritized issues + improvement plan
- On approval: Implement changes using references/improvement-patterns.md
- Verify: Re-grade to confirm improvements
Grading Checklist
Copy and track progress:
Evaluation Progress:
- [ ] Step 1: Detect CLAUDE.md and AGENTS.md files
- [ ] Step 2: Measure size (lines, bytes, tokens)
- [ ] Step 3: Score Structure (25 pts)
- [ ] Step 4: Score Content Quality (25 pts)
- [ ] Step 5: Score PDA Implementation (25 pts)
- [ ] Step 6: Score Maintainability (25 pts)
- [ ] Step 7: Apply modifiers (±10 pts)
- [ ] Step 8: Generate report with grade
- [ ] Step 9: List improvements with priority
- [ ] Step 10: Ask: "Implement these improvements?"
Score Summary
Base: Structure (25) + Content (25) + PDA (25) + Maintainability (25) = 100 pts Modifiers: ±10 pts for bonuses/penalties Final: Capped at 0-100
| Grade | Score | Meaning |
|---|---|---|
| A | 90-100 | Excellent, minimal changes needed |
| B | 80-89 | Good, minor improvements recommended |
| C | 70-79 | Adequate, notable issues to fix |
| D | 60-69 | Poor, significant refactoring needed |
| F | <60 | Critical, major overhaul required |
Reference Files
| Reference | When to Read |
|---|---|
| references/rubric.md | Scoring all criteria |
| references/improvement-patterns.md | Implementing fixes |
| references/size-guide.md | Understanding thresholds |
Implementation Workflow
After grading, if user approves improvements:
- Backup: Copy original to
CLAUDE.md.backup - Create structure: Add subdirectory configs if needed
- Extract content: Move sections to reference files
- Add TOC: Generate table of contents for files >100 lines
- Update imports: Add @imports for extracted content
- Validate: Run size check on new structure
- Report: Show before/after comparison
What Gets Fixed Automatically
| Issue | Fix Applied |
|---|---|
| File too large (>500 lines) | Split into subdirectory configs or docs/ |
| Missing TOC (>100 lines) | Generate and insert table of contents |
| No @imports for large sections | Extract to docs/*.md, add @imports |
| Style rules in config | Move to linter config, add pointer |
| Negative-only rules | Add "instead use X" alternatives |
| Duplicate content | Consolidate to single location |
| Monorepo without subdirs | Create package-level CLAUDE.md files |
Output Format
Grade report structure:
# Config Grade Report: [filename]
## Score: XX/100 (Grade: X)
| Pillar | Score | Max |
|--------|-------|-----|
| Structure | XX | 25 |
| Content Quality | XX | 25 |
| PDA Implementation | XX | 25 |
| Maintainability | XX | 25 |
| Modifiers | ±X | ±10 |
## Top Issues (prioritized)
1. **[Issue]**: [Description] → [Fix]
Impact: +X pts if fixed
2. **[Issue]**: [Description] → [Fix]
Impact: +X pts if fixed
## Recommended Actions
- [ ] Action 1
- [ ] Action 2
- [ ] Action 3
---
**Implement these improvements? (y/n)**
When Not to Use
Do not use this skill for:
- Creating new skills (use skill-creator)
- General markdown editing
- README.md or documentation files
- System prompts or prompt engineering
- MCP server configuration
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
SpillwaveSolutions/spacy-nlp-agentic-skill
using-spacy-nlp
Industrial-strength NLP with spaCy 3.x for text processing and custom classifier training. Use when "installing spaCy", "selecting model for nlp" (en_core_web_sm/md/lg/trf), "tokenization", "POS tagging", "named entity recognition" (NER), "dependency parsing", "training TextCategorizer models", "troubleshooting spaCy errors" (E050/E941 model errors, E927 version mismatch, memory issues), "batch processing with nlp.pipe", or "deploying nlp models to production". Includes data preparation scripts, config templates, and FastAPI serving examples.
SpillwaveSolutions/publishing-astro-websites-agentic-skill
publishing-astro-websites
Comprehensive guidance for building and deploying static websites with the Astro framework. This skill should be used when asked to "create astro site", "deploy astro to firebase", "set up content collections", "add mermaid diagrams to astro", "configure astro i18n", "build static blog", or "astro markdown setup". Covers SSG fundamentals, Content Collections, Markdown/MDX, partial hydration, islands architecture, and deployment to Netlify, Vercel, GitHub Pages, or GCP/Firebase.
SpillwaveSolutions/agent-brain
configuring-agent-brain
Installation and configuration skill for Agent Brain document search system. Use when asked to "install agent brain", "setup agent brain", "configure agent brain", "setting up document search", "installing agent-brain packages", "configuring API keys", "initializing project for search", "troubleshooting agent brain", "pip install agent-brain", "agent brain not working", "agent brain setup error", "configure embeddings provider", "setup ollama for agent brain", or "agent brain environment variables". Covers package installation, provider configuration, project initialization, and server management.
SpillwaveSolutions/agent-brain
using-agent-brain
Expert Agent Brain skill for document search with BM25 keyword, semantic vector, hybrid, graph, and multi retrieval modes. Use when asked to "search documentation", "query domain", "find in docs", "bm25 search", "hybrid search", "semantic search", "graph search", "multi search", "find dependencies", "code relationships", "searching knowledge base", "querying indexed documents", "finding code references", "exploring codebase", "what calls this function", "find imports", "trace dependencies", "brain search", "brain query", "knowledge base search", "cache management", "clear embedding cache", "cache hit rate", or "cache status". Supports multi-instance architecture with automatic server discovery. GraphRAG mode enables relationship-aware queries for code dependencies and entity connections. Pluggable providers for embeddings (OpenAI, Cohere, Ollama) and summarization (Anthropic, OpenAI, Gemini, Grok, Ollama). Supports multiple runtimes (Claude Code, OpenCode, Gemini CLI) with shared .agent-brain/ data directory.
SpillwaveSolutions/agent-brain
uat-testing
SpillwaveSolutions/agent-brain
installing-local
Didn't find tool you were looking for?