brain-check
Skill1 starsChanged 5 months agoMITView on GitHub
System health review. Identifies orphaned notes, popular ghost links, missing frontmatter, taxonomy suggestions, and connection opportunities.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- zl3311/alpha-miningtheir own version, first seen Jul 25, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- zl3311/alpha-mining★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- brain-addSkill
- brain-add-videoSkill
- brain-digestSkill
- brain-processSkill
- brain-saveSkill
- brain-searchSkill
- client-onboardSkill
- consulting-deckSkill
- good-morningSkill
- harvestSkill
- logSkill
- taskSkill
- weekly-reviewSkill
- wrap-sessionSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 39
Check if any notes exist outside the expected category tree
- Distinctive: line 40
If a subcategory has grown significantly, suggest splitting or reorganizing
- Distinctive: line 41
Check for tags used in notes but NOT in brain-config.md vocabulary → suggest adding them
- Distinctive: line 49
Check existing MOCs in mocs/ — are they up to date?
- Very specific: line 52
Update mocs/_Index.md if new MOCs were created
- Very specific: line 83
Verify brain/index.md exists and is up to date
- Distinctive: line 85
If index is missing entries, offer to rebuild it
- Distinctive: line 88
Use Bash to append directly without reading:
- Distinctive: line 105
When offering fixes, batch them and confirm before executing.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
/brain-check
System health review and improvement suggestions.
Steps
- Read
brain-config.md(taxonomy, tags) andbrain-config-rules.md(MOC thresholds, ghost link rules). - Ghost link analysis:
- Grep all .md files in brain/ for
[[...]]wiki-links - Build a map of all referenced topics
- Identify ghost links (referenced but no backing .md file exists)
- Count references per ghost link
- Flag ghost links with 3+ references → suggest creating a MOC
- Flag ghost links with 5+ references → strongly recommend MOC or dedicated note
- Grep all .md files in brain/ for
- Orphaned note check:
- For each note, check if any OTHER note links to it (via [[wiki-link]] or
related:field) - Notes with zero incoming references are orphaned
- Suggest connections based on shared tags or content similarity
- For each note, check if any OTHER note links to it (via [[wiki-link]] or
- Frontmatter audit:
- Scan all notes for YAML frontmatter completeness
- Flag missing fields: title, type, tags, source, created, status, category, summary
- Flag notes with empty tags array
- Flag notes still at
seedstatus older than 14 days → suggest enriching
- Taxonomy health:
- Count notes per subcategory
- Flag subcategories with 0 notes (empty) or 10+ notes (might need splitting)
- Check if any notes exist outside the expected category tree
- If a subcategory has grown significantly, suggest splitting or reorganizing
- Check for tags used in notes but NOT in brain-config.md vocabulary → suggest adding them
- Connection opportunities:
- Find notes with shared tags that aren't linked to each other
- Find notes that reference the same ghost links but don't know about each other
- Suggest adding
related:links or inline [[wiki-links]]
- MOC maintenance:
- Check existing MOCs in mocs/ — are they up to date?
- For each MOC, verify all notes that reference its topic are listed
- Identify notes that should be in an MOC but aren't linked
- Update
mocs/_Index.mdif new MOCs were created
Present the health report:
🔧 Brain Health Check — {date} ## Ghost Links (unresolved [[references]]) ⚡ 3+ refs (suggest MOC): - [[Topic A]] — referenced by {X} notes - [[Topic B]] — referenced by {X} notes 👻 Under threshold: - [[topic]] — {X} refs ## Orphaned Notes (no incoming links) - {title} ({category}) — suggest connecting to: {related notes} ## Frontmatter Issues - {filename}: missing {fields} - {filename}: seed status for {X} days ## Taxonomy Suggestions - {subcategory}: {X} notes — consider splitting into... - New tags to add to vocabulary: #tag1, #tag2 ## Connection Opportunities - {note A} ↔ {note B}: shared #tag but not linked- Index health check:
- Verify
brain/index.mdexists and is up to date - Compare notes on disk vs entries in index — flag any missing or stale entries
- If index is missing entries, offer to rebuild it
- Verify
- Append to log.md (do NOT read the file — append only):
- Use Bash to append directly without reading:
echo '## [YYYY-MM-DD] lint | brain-check Found: {X} ghost links at threshold, {X} orphaned notes, {X} frontmatter gaps, {X} index mismatches. ' >> brain/meta/log.md
- Use Bash to append directly without reading:
- Offer to fix:
- "Want me to create MOCs for the 3+ ref ghost links?"
- "Want me to add missing frontmatter fields?"
- "Want me to connect orphaned notes?"
- "Want me to rebuild/update the index?"
- Execute fixes for any the user approves
Important
- This is a READ-HEAVY operation. In depleted context, suggest running in a fresh session.
- When offering fixes, batch them and confirm before executing.
- For taxonomy changes (new subcategories, restructuring), always ask before modifying brain-config.md.
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
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.

