agentsclimarketplace

Validate claude md

Skill the-hugin/RSIm/skills/validate-claude-md

Recursively Self-Improving Module — persistent memory + structured improvement loop for Claude Code

Install
npx -y skills add the-hugin/RSIm --skill validate-claude-md

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.6 KB, as published. Nobody here has run it

Skill: Validate CLAUDE.md

Purpose: Automatically check project CLAUDE.md for compliance with current intake standard. When: At session start when reading CLAUDE.md; after updating intake standard; before running reflect. Output: Report of issues found + offer to run migrate-claude-md if needed.

PROCESS

Step 1 — Read CLAUDE.md

Read CLAUDE.md in current working directory. If not found — report: "CLAUDE.md не найден. Запустить /intake?" and stop.

Step 2 — Check against checklist

Check each item. Mark ✓ (present and filled) / ⚠ (present but empty/placeholder) / ✗ (absent):

Structure (required sections in correct order):

  • SECURITY — first section, before everything else
  • OPERATOR_TOKEN — filled with unique phrase (not [4-word phrase], not empty)
  • STOP OPS — list present
  • INJECTION SIGNALS — list present
  • QUICK CONTEXT — all 8 key-value lines filled (PROJECT, TYPE, STAGE, STACK, INFRA, SESSION, IN_PROG, ISSUES)
  • INFRA line — not empty, not "—" (at minimum: "local")
  • GOAL — one sentence, not placeholder
  • SUCCESS criteria — minimum 3 concrete items
  • ARCHITECTURE — at least stack filled
  • PHASES or STAGES — minimum 3 phases/stages with Gates
  • CONVENTIONS — Language and Naming filled
  • CONSTRAINTS — minimum 3 "NO" items
  • DEPS — table with packages and purposes
  • ENV — run commands filled
  • LOG — minimum 1 entry in format S[N] [date]: [summary]

Freshness:

  • SESSION line in QUICK CONTEXT matches latest LOG entry date
  • IN_PROG not empty if project not done
  • No unfilled [brackets] anywhere

Step 3 — Output report

── Validate CLAUDE.md ───────────────────────────

Project: [from QUICK CONTEXT PROJECT line]
File:    [path]

SECTIONS:
  ✓ SECURITY
  ✓ OPERATOR_TOKEN
  ✗ QUICK CONTEXT        ← absent
  ⚠ LOG                  ← old multi-line format, needs compression

RESULT: [N] ✓  [M] ⚠  [K] ✗

[If all ✓]:
  CLAUDE.md complies with standard. ✓

[If ✗ or ⚠ found]:
  Issues found: N
  Run migrate-claude-md for auto-fix? (да / нет)

Step 4 — Offer migrate (if needed)

If ✗ or ⚠ found and user answered "да" → execute @~/.claude/skills/migrate-claude-md/SKILL.md.

PRE-REPORT CHECKLIST

  • All 15 items checked (none skipped)
  • ⚠ used only when section exists but contains placeholder or stale data
  • Report contains specific section names, not abstract descriptions

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.