coherence-sweep
Skill109 starsChanged 38 days agoMITView on GitHub
Run a full coherence sweep across the Brain Dependency Graph - computes staleness, lifecycle transitions, structural health, and generates a report
In this repository61 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adviseSkill
- ai-crystallizeSkill
- analyze-kbSkill
- auto-discoverySkill
- benchmark-memorySkill
- brain-mergeSkill
- changelog-protocolSkill
- compute-lifecycleSkill
- create-articleSkill
- create-explanatory-imageSkill
- decideSkill
- deep-researchSkill
- detect-tensionsSkill
- dialecticSkill
- domain-watchSkill
- elicitation-techniquesSkill
- epistemic-classificationSkill
- epub-chapter-extractorSkill
- extract-document-insightsSkill
- extract-insightsSkill
- find-connectionsSkill
- first-runSkill
- get-perspective-onSkill
- get-youtube-transcriptSkill
- git-commit-pushSkill
- graduate-insightsSkill
- incubation-loopSkill
- ingest-sourceSkill
- insight-capture-formatSkill
- insight-interviewSkill
- integrate-recent-notesSkill
- learn-new-thingsSkill
- manage-reference-dataSkill
- manage-thinking-topicsSkill
- manage-watching-domainsSkill
- multi-format-book-extractorSkill
- nano-banana-image-generatorSkill
- propagate-changeSkill
- quick-searchSkill
- reasoning-checksSkill
- recallSkill
- ref-auditSkill
- ref-bridgeSkill
- ref-ingestSkill
- ref-querySkill
- ref-reconcileSkill
- ref-refreshSkill
- refresh-indexSkill
- ref-supersedeSkill
- scheduled-runSkill
- scope-mountSkill
- search-vaultSkill
- self-diagnosticSkill
- start-hereSkill
- synthesize-insightsSkill
- talkSkill
- test-memory-systemSkill
- think-about-itSkill
- update-changelogSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
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
- Distinctive: line 12
Run a full coherence analysis of the knowledge base using the Brain Dependency Graph engine.
- Distinctive: line 36
If not bootstrapped, run bootstrap first:
- Distinctive: line 43
Default (7-day lookback, lifecycle included, no tensions):
- Distinctive: line 62
Read the generated report and present key findings to the user:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 Coherence Sweep
Run a full coherence analysis of the knowledge base using the Brain Dependency Graph engine. Identifies stale notes, lifecycle transitions, structural issues, and optionally productive tensions.
State Dependencies
| Source | Location | Read | Write | Description |
| LBS Graph | resources/local-brain-search/data/brain_graph.pkl | ✓ | NetworkX graph | |
| Enrichments | resources/brain-graph/data/graph_enrichments.json | ✓ | ✓ | Node/edge enrichments |
| Reports | resources/brain-graph/reports/ | ✓ | Generated reports |
Prerequisites
- Brain Dependency Graph must be bootstrapped (
run_brain_graph.sh bootstrap) - Local Brain Search index must exist
Process
Step 1: Check bootstrap status
cd $PROJECT_ROOT/resources/brain-graph
../local-brain-search/venv/bin/python cli.py statusIf not bootstrapped, run bootstrap first:
../local-brain-search/venv/bin/python cli.py bootstrapStep 2: Run coherence sweep
Default (7-day lookback, lifecycle included, no tensions):
../local-brain-search/venv/bin/python cli.py coherenceWith options:
# Include tension detection (slower)
../local-brain-search/venv/bin/python cli.py coherence --tensions
# Custom lookback period
../local-brain-search/venv/bin/python cli.py coherence --days 14
# JSON output
../local-brain-search/venv/bin/python cli.py coherence --jsonStep 3: Present results
Read the generated report and present key findings to the user:
- Staleness alerts - Notes that need review due to upstream changes
- Lifecycle transitions - Notes crossing phase boundaries (reflective -> crystallizing -> generative)
- Structural health - Orphans, overloaded hubs, missing MOCs
- Tensions (if enabled) - Productive contradictions for synthesis
Report is saved to: resources/brain-graph/reports/coherence-report-YYYY-MM-DD.md
Output Format
Present a concise summary with:
- Count of stale notes with top 5 most affected
- Notable lifecycle transitions (especially new generative notes)
- Structural issues requiring attention
- Path to full report
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.

