Skip to content
Back to skills

Validate Claude Md

ASecurity

**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. ---

  • 2 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 27, 2026
data-aigosecurity

Security analysis

A100/100

Scanned May 27, 2026

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

Installs into .claude/skills of the current project.

Are you the author of Validate Claude Md?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Validate Claude Md
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/the-hugin-validate-claude-md/badge)](https://www.skillsdirectory.com/skills/the-hugin-validate-claude-md)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
# 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

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.