agentleFS
Sign inStart free
xeevaxeeva/Genesis/.claude/skills/validate/SKILL.md

validate

Skill17 starsChanged 8 months agoMITView on GitHub

Validate that a generated project's Claude infrastructure is complete and well-formed. Use when the user says "validate", "check project", or "verify".

63 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use policy-init, create and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • open-coder-aiSkill

    policy-init

    Create conformant Chock policy from request. args(request, target_path,

    Also in 3 projects that use this

  • MicrosoftSkill

    create

    Also in 4 projects that use this

  • HermeticOrmusSkill

    close

    End-of-session ritual. Captures session state, updates auto-memory, writes a session summary, then exits the session cleanly.

    Also in 4 projects that use this

  • Hugging FaceSkill

    sprint

    Work on a batch of GitHub issues in parallel using Agent Teams. Creates one worktree per issue with TDD enforcement, coordinates via a lead agent, then produces stacked PRs.

    Also in 4 projects that use this

  • qtzx06Skill

    eval

    Evaluate trained YOLO model accuracy with mAP metrics and per-class error analysis. Identifies failure cases for targeted improvement. Use after training.

    Also in 4 projects that use this

  • csiddhant796-blipSkill

    board

    Read, write, and browse the AgentHub message board for agent coordination.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 53 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check that a target project directory has all expected Claude Code infrastructure files and that they are well-formed.

    line 10
  2. Distinctive:

    If all checks pass: "Project is fully configured and ready to use." If checks fail: list the failures with specific remediation steps.

    line 62
  3. Distinctive:

    If checks fail: list the failures with specific remediation steps.

    line 63

“Common” is measured: kept by at least 6 in 10 of the 53 edited versions of this file we could read. “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

Project Validator

Check that a target project directory has all expected Claude Code infrastructure files and that they are well-formed.

Usage

The user provides a project name or path. Default to the most recently created project if none specified.

Checks

Required Files

  • CLAUDE.md exists and is non-empty
  • .claude/settings.json exists and is valid JSON
  • .claude/agents/ directory has at least 3 agent files (test-runner, code-reviewer, doc-writer)
  • .claude/skills/ directory has at least 4 skill directories (test, lint, review, commit)
  • Each skill directory contains a SKILL.md with valid YAML frontmatter
  • docs/README.md exists
  • docs/architecture.md exists
  • .gitignore exists
  • Git repo is initialised (.git/ exists)

Memory Files

  • ~/.claude/projects/-home-xeeva-claude-<name>/memory/MEMORY.md exists
  • ~/.claude/projects/-home-xeeva-claude-<name>/memory/user-profile.md exists
  • ~/.claude/projects/-home-xeeva-claude-<name>/memory/project-context.md exists

Content Quality

  • CLAUDE.md contains "Australian English" rule
  • CLAUDE.md contains "em dash" rule
  • CLAUDE.md contains "fail fast" or error handling section
  • CLAUDE.md contains testing section
  • settings.json has permissions.allow array
  • settings.json has at least one hook

Optional Files

  • .mcp.json exists if integrations were specified (report if missing but expected)
  • Stack-specific config files exist (tsconfig.json, pyproject.toml, etc.)

Output

Report results as a checklist:

Validating: ~/claude/<name>/

Required Files:        [12/12 passed]
Memory Files:          [3/3 passed]
Content Quality:       [5/6 passed]
  - MISSING: settings.json has no hooks configured
Optional Files:        [2/2 passed]

Overall: 22/23 checks passed

If all checks pass: "Project is fully configured and ready to use." If checks fail: list the failures with specific remediation steps.

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.

Check your setup, free