auto-discovery
Skill109 starsChanged 38 days agoMITView on GitHub
Discover non-obvious cross-domain connections through random sampling and pattern analysis
1 other project uses a version of this.
Adopted by
Most recently taken up by
- 0oooooooo0/skilllesstheir own version, first seen Mar 6, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- 0oooooooo0/skillless★ 38same 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 repository61 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adviseSkill
- ai-crystallizeSkill
- analyze-kbSkill
- 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
- 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
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 47
Use for changelog filename.
- Distinctive: line 78
Read both notes fully
- Very specific: line 132
Add brief summary to Brain/CHANGELOG.md:
≈ “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
Auto-Discovery
Autonomous cross-domain connection hunter. Samples notes from different thematic clusters and finds meaningful relationships that semantic similarity alone would miss.
Purpose
Find non-obvious, cross-domain connections - notes with modest semantic similarity but high conceptual strength. These are the hidden patterns in the knowledge base.
Calibration correction (2026-09-02). This skill's historic sweet spot of "0.50-0.70 = the non-obvious tail" was inverted: measured on the live index, 0.50-0.70 is the typical band (median best-neighbour 0.724 vault-wide), and the 0.85+ band it told you to skip as "too obvious" is dominated by boilerplate twins rather than real conceptual overlap. The discriminator was never the number - it is cross-domain reasoning after reading the notes. Use similarity only to assemble a candidate pool, never to grade a discovery. Contract + live figures:
resources/local-brain-search/SIMILARITY-CALIBRATION.md.
State Dependencies
| Source | Location | Read | Write | Description |
| Permanent Notes | Brain/02-Permanent/ | ✓ | Sampling source | |
| AI Extracted Notes | Brain/AI Extracted Notes/ | ✓ | Sampling source | |
| Document Insights | Brain/Document Insights/ | ✓ | Sampling source | |
| Local Brain Search | resources/local-brain-search/ | ✓ | Similarity scores, connections | |
| Session Changelogs | Brain/05-Meta/Changelogs/ | ✓ | Dated discovery log | |
| Master Changelog | Brain/CHANGELOG.md | ✓ | ✓ | Summary entry |
Prerequisites
- Local Brain Search index up-to-date (
/refresh-index) - Brain vault accessible
Process
Step 1: Get Current Date
date '+%Y-%m-%d'Use for changelog filename.
Step 2: Strategic Sampling
Sample from 3-5 diverse domains using Local Brain Search:
# --no-track: autonomous weekly loop; its cross-domain samples must NOT train q-values (scope-primitive learning hygiene).
# BRAIN_READ_SCOPE=<wide>: cross-domain (non-core) sampling is this skill's PURPOSE, so it must read past
# the core fingerprint. Set it wide rather than letting it fail closed to core once enforcement is on.
# Only the learn axis is closed (--no-track); the read axis is deliberately wide.
BRAIN_READ_SCOPE=core,Books,document-insights,meta,inbox,output resources/local-brain-search/run_search.sh "dopamine" --limit 5 --no-track --json
BRAIN_READ_SCOPE=core,Books,document-insights,meta,inbox,output resources/local-brain-search/run_search.sh "uncertainty" --limit 5 --no-track --json
BRAIN_READ_SCOPE=core,Books,document-insights,meta,inbox,output resources/local-brain-search/run_search.sh "identity" --limit 5 --no-track --jsonPick seed notes from different clusters.
Step 3: Get Connections for Seeds
For each seed note (same wide read-scope - the seeds and their neighbors live across domains):
BRAIN_READ_SCOPE=core,Books,document-insights,meta,inbox,output resources/local-brain-search/run_connections.sh "Note Name" --jsonIdentify notes with similarity ~0.45-0.70 from DIFFERENT domains (candidate pool - see the calibration correction above).
Step 4: Cross-Domain Analysis
For each cross-domain pair:
- Read both notes fully
- Record ACTUAL similarity score from search
- Analyze for:
- Shared structural patterns
- Common mechanisms
- Meta-principles
- Paradoxes
Rate conceptual strength (1-5 stars).
Target: Low semantic similarity + high conceptual strength = valuable discovery.
Step 5: Document Discoveries
For each strong connection:
## CROSS-DOMAIN CONNECTION
**Node A**: [[Note X]] (Domain: Neuroscience)
**Node B**: [[Note Y]] (Domain: Economics)
**Semantic Similarity**: 0.63 (actual from search)
**Conceptual Strength**: ⭐⭐⭐⭐⭐
**The Link**: [2-3 sentences explaining WHY they connect]
**Shared Pattern**: [The underlying principle]
**Synthesis Opportunity**: [Potential new note title]Step 6: Create Dated Changelog
Write to Brain/05-Meta/Changelogs/CHANGELOG - Auto-Discovery Session YYYY-MM-DD.md:
## Auto-Discovery Session: YYYY-MM-DD
### Session Parameters
- Notes sampled: [N] from [X] clusters
- Domains analyzed: [list]
### Discoveries Made
**Strong Connections**: [N]
1. [[A]] ↔ [[B]] - [pattern]
**Meta-Patterns**: [N]
**Consilience Zones**: [N]
### Session Statistics
- Total notes analyzed: [N]
- Non-obvious connections (similarity < 0.70): [N] ← report the count, but note this is near the median on this index, not the tailStep 7: Update Master Changelog
Add brief summary to Brain/CHANGELOG.md:
## YYYY-MM-DD - Auto-Discovery Session
See: [[CHANGELOG - Auto-Discovery Session YYYY-MM-DD]]
- [N] connections discovered
- [N] meta-patterns identifiedQuality Standards
GOOD discoveries:
- Semantic similarity roughly 0.45-0.70 (a pool, not a grade - see the calibration note above)
- Clear conceptual link across domains
- "Aha!" factor - non-obvious insight
- Actionable synthesis opportunity
SKIP:
- High similarity (0.85+) - usually shared boilerplate (frontmatter/changelog twins), not insight
- Same domain - not cross-domain
- Already linked in vault
Error Handling
| Error | Recovery |
| Search returns empty | Try different seed terms |
| All high similarity | Note in changelog, try broader clusters |
| Index outdated | Run /refresh-index first |
Completion Checklist
- Notes sampled from 3+ different clusters
- ACTUAL similarity scores recorded (not estimated)
- Cross-domain connections with conceptual analysis
- Non-obvious discoveries documented (similarity < 0.70) and justified by cross-domain reasoning, not by the score alone
- Dated changelog created in
Brain/05-Meta/Changelogs/ - Master changelog updated with summary
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.

