메뉴
Confirms the Clankbrain install worked. Run this right after setup or anytime you suspect something is broken. Triggers on "kit health", "is the kit installed", "kit check", "did install work", "verify kit", "health check kit".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Scans a real codebase and writes coding-conventions.md from what it actually finds — variable style, SQL patterns, error handling, INSERT strategy, naming. Run once on any new project to bootstrap the convention system. Triggers on "scan conventions", "generate conventions", "bootstrap conventions", "extract conventions from code", "what are the conventions".
Security audit — checks auth, SQL injection, exposed endpoints, and sensitive data. Triggers on "security check", "is this secure", "check for vulnerabilities", "check auth", "audit security", "security audit".
Use when switching environments, updating config values, or verifying URLs/settings. Triggers on "check environment", "switch to production", "update URLs", "check config", "is this prod-ready".
Use when verifying a feature works, after making changes, or before shipping. Triggers on "verify this works", "test this", "does this work", "run the checklist", "before I ship", "check this end to end".
Use when cleaning up, simplifying, or restructuring existing code without changing behavior. Triggers on "refactor", "clean up", "simplify this", "this is getting messy", "too long", "hard to read", "extract this".
Use when the user wants to review a file for bugs, antipatterns, or quality issues. Triggers on "review", "check for issues", "look for problems", "audit", "before I ship".
| name | kit-health |
| description | Confirms the Clankbrain install worked. Run this right after setup or anytime you suspect something is broken. Triggers on "kit health", "is the kit installed", "kit check", "did install work", "verify kit", "health check kit". |
| allowed-tools | Read, Glob, Bash |
Run after setup.py finishes, or anytime the user asks "did install work" / "is the kit healthy" / "kit check".
Inspects the Clankbrain install, confirms each piece is in place, and reports a green/red status for each. Builds confidence that install succeeded — the most important first impression.
Find the kit root. Either:
.claude/ exists (shared memory root for both apps)Check each piece. Report green/red for each.
== Clankbrain Health Check ==
Memory directory [check .claude/memory/ exists]
Skills loaded [count .claude/skills/*/SKILL.md files]
Hooks active [parse .claude/settings.json, count hooks]
Starter lessons [check .claude/memory/lessons.md is non-empty]
Memory index [check .claude/memory/MEMORY.md exists]
Settings file [check .claude/settings.json valid JSON]
Tools directory [check tools/ exists with memory.py]
Sync configured [check sync.py exists, optional check for git remote]
Overall: [PASS / FAIL with X issues]
For each FAIL, give a specific fix:
python setup.py"python setup.py".claude/settings.json.bak"tour to see the kit work with starter content."End with the next step:
✓ Install verified.
Next: Type "tour" for a 5-minute walkthrough,
or "Start Session" to begin working.
ls .claude/skills/*/SKILL.md 2>/dev/null | wc -l
python -c "import json; json.load(open('.claude/settings.json'))" 2>&1
Exit 0 = valid. Non-zero = invalid.
Read .claude/settings.json, count entries in hooks object across all hook types (PreToolUse, PostToolUse, Stop, PreCompact, etc.).
Use ✓ for pass, ✗ for fail, with green/red mental colors via emoji or text formatting.
== Clankbrain Health Check ==
✓ Memory directory .claude/memory/ (12 files)
✓ Skills loaded 32 of 32
✓ Hooks active 8 hooks across 5 events
✓ Starter lessons 3 entries
✓ Memory index MEMORY.md (118 lines)
✓ Settings file valid JSON
✓ Tools directory memory.py present
○ Sync configured skipped (optional — run `python sync.py setup` to enable)
Overall: PASS — 7/7 required checks green
Optional: 1 skipped (sync — only if you want GitHub backup)
Next: Type "tour" for a 5-minute walkthrough, or "Start Session" to begin.
Be specific. Don't just say "broken." Tell the user:
Example:
✗ Skills loaded: 0 of 32 expected
Why this matters: All the magic is in the skills. Without them, the kit is just a folder.
Fix: Run `python setup.py --force` to re-install skills.
If that fails, check that you cloned the full repo (not a sparse checkout).
A new user's first 60 seconds with the kit determine whether they keep going. This matters even more now that people may open the same repo in Claude or Codex. Without this skill, install is silent — they don't know if it worked. With this skill, they get instant confirmation + a clear next step.