integrate-recent-notes
Skill109 starsChanged 37 days agoMITView on GitHub
Find notes created in the last 14 days and discover their connections to the knowledge base
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
- coherence-sweepSkill
- 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
- 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
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 57
Run connection discovery (wide read-scope: recent notes live in 00-Inbox / Document Insights / Books / 05-Meta - core-only would fail to …
- Distinctive: line 58
Document Insights / Books / 05-Meta - core-only would fail to resolve the note itself or its non-core neighbors once scope enforcement is …
- Distinctive: line 64
Check BDG layer classification:
≈ “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
Integrate Recent Notes
Find recently created notes and map their connections to the existing knowledge base.
Purpose
New notes often sit unconnected. This playbook identifies notes from the last 14 days and discovers how they integrate with existing knowledge.
State Dependencies
| Source | Location | Read | Write | Description |
| Permanent Notes | Brain/02-Permanent/ | ✓ | Recent notes source | |
| AI Extracted Notes | Brain/AI Extracted Notes/ | ✓ | Recent notes source | |
| Document Insights | Brain/Document Insights/ | ✓ | Recent notes source | |
| Book scopes | Brain/Books/ | ✓ | Recent notes source (per-book scopes) | |
| Local Brain Search | resources/local-brain-search/ | ✓ | Connection discovery | |
| Session Changelogs | Brain/05-Meta/Changelogs/ | ✓ | Integration report |
Prerequisites
- Local Brain Search index up-to-date (
/refresh-index)
Process
Step 1: Find Recent Notes
Find notes modified in the last 14 days:
find Brain/02-Permanent -name "*.md" -mtime -14 -type f
find Brain/AI\ Extracted\ Notes -name "*.md" -mtime -14 -type f
find Brain/Document\ Insights -name "*.md" -mtime -14 -type f
find Brain/Books -name "*.md" -mtime -14 -type fCompile list of recent notes.
Step 2: Get Current Date
date '+%Y-%m-%d'Step 3: Analyze Connections for Each
For each recent note:
- Extract note title from filename
- Run connection discovery (wide read-scope: recent notes live in 00-Inbox /
Document Insights / Books / 05-Meta - core-only would fail to resolve the note
itself or its non-core neighbors once scope enforcement is on):
BRAIN_READ_SCOPE=core,Books,document-insights,meta,inbox,output resources/local-brain-search/run_connections.sh "Note Title" --json - Record top 5 connections with similarity scores
- Check BDG layer classification:
resources/brain-graph/run_brain_graph.sh inspect "Note Title" --json
Step 4: Identify Integration Opportunities
For each note, categorize:
- Well-connected (3+ connections > 0.70): Already integrated
- Partially connected (1-2 connections > 0.70): Needs attention
- Isolated (0 connections > 0.70): Priority for integration
Step 5: Create Integration Report
Write to Brain/05-Meta/Changelogs/CHANGELOG - Note Integration YYYY-MM-DD.md:
## Note Integration Report: YYYY-MM-DD
### Recent Notes Analyzed
Total: [N] notes from last 14 days
### Integration Status
**Well-Connected** ([N]):
- [[Note A]] - 5 connections
**Partially Connected** ([N]):
- [[Note B]] - 2 connections
- Suggested: Link to [[X]], [[Y]]
**Isolated - Priority** ([N]):
- [[Note C]] - 0 connections
- Top semantic matches: [[X]] (0.65), [[Y]] (0.62)
- Integration suggestion: [brief recommendation]
### Suggested Actions
1. [specific linking recommendations]
2. [synthesis opportunities]Outputs
- Integration report in
Brain/05-Meta/Changelogs/ - List of isolated notes needing attention
- Suggested connections for each
Error Handling
| Error | Recovery |
| No recent notes | Log "no notes in period" and exit |
| Connection search fails | Note error, continue with next note |
| Index outdated | Run /refresh-index first |
Completion Checklist
- Recent notes identified (last 14 days)
- Connections analyzed for each note
- Notes categorized (well-connected, partial, isolated)
- Integration suggestions provided for isolated notes
- Report created in
Brain/05-Meta/Changelogs/
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.

