agentleFS
claude-worldclaude-world/director-mode-lite/skills/claude-md-check/SKILL.md

claude-md-check

Skill80 starsChanged 8 months agoMITView on GitHub

Validate CLAUDE.md structure and completeness

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If issues found, offer to:

    line 57
  2. Distinctive:

    Add missing sections with placeholders

    line 58
  3. Very specific:

    Update tech stack from package.json

    line 59
  4. Distinctive:

    Verify and correct commands

    line 60

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CLAUDE.md Validator

Validate the project's CLAUDE.md file for completeness and best practices.


Validation Checklist

Required Sections (Must Have)

  • Project Overview - Brief description
  • Tech Stack - Languages, frameworks, tools
  • Commands - dev, test, build commands

Recommended Sections (Should Have)

  • Conventions - Coding standards
  • Key Files - Important files
  • Architecture - Directory structure

Quality Checks

  • No secrets - No API keys in file
  • Correct commands - Listed commands work
  • Up to date - Matches actual dependencies

Output Format

## CLAUDE.md Validation Report

### Status: PASS / NEEDS IMPROVEMENT / MISSING

### Required Sections
| Section | Status | Notes |
|---------|--------|-------|
| Project Overview | | |
| Tech Stack | | |
| Commands | | |

### Issues Found
1. [Issue and how to fix]

### Suggestions
1. [Improvement]

Auto-Fix

If issues found, offer to:

  • Add missing sections with placeholders
  • Update tech stack from package.json
  • Verify and correct commands

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.