insight-capture-format
Skill109 starsChanged 38 days agoMITView on GitHub
Standard format for capturing and documenting insights in the knowledge base. Use when harvesting insights, creating permanent notes from user perspectives, or documenting unique thinking patterns.
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-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, 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 9
When capturing an insight, use this format:
- Distinctive: line 55
Non-redundant: No duplicate insights - always search before creating
- Distinctive: line 57
Non-contradicting: When conflicts arise, resolve or document the tension explicitly
≈ “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
Insight Capture Format
When capturing an insight, use this format:
> **[CAPTURING INSIGHT]**
>
> **Title:** `[[Concise title that captures the unique perspective]]`
> **Type:** (Personal Theory / Contrarian View / Synthesis / Experience Wisdom / Mental Model / Pattern / Value Discovery / Reading Reflection)
> **Uniqueness:** What makes this insight distinctively yours
> **Source:** [If from reading: Book/Article title, Author, Page/Location]
>
> ---
>
> [Body: The insight in 1-3 sentences, preserving your authentic voice and reasoning]
>
> ---
> **Connections:**
> * `[[Related Insight]]` - how this builds on previous thinking
> * `[[Contrasts With]]` - ideas this challenges or refines
> * `[[Examples]]` - concrete instances that demonstrate this
> * `[[Questions Raised]]` - what this makes you wonder about
>
> **Keywords:** #insight-type #topic #source-if-applicableInsight Types to Harvest
Actively hunt for and categorize these types of unique insights:
| Type | Description | Example Signal |
| Personal Theory | Original explanatory models | "I think X works because Y" |
| Contrarian View | Challenges conventional wisdom | "Everyone says X, but I've found Y" |
| Synthesis Insight | Novel connections between concepts | "A is like B in this unexpected way" |
| Experience Wisdom | Hard-won lessons | "After failing at X multiple times, I realized Y" |
| Mental Model | Unique cognitive frameworks | "I always approach X by thinking of it as Y" |
| Pattern Recognition | Personal observations | "I've noticed that whenever X happens, Y follows" |
| Value Discovery | Evolution of priorities | "I used to think X mattered, but now Y is what counts" |
| Reading Reflection | Thoughts from books/articles | With proper source attribution |
Knowledge Base Integrity Principles
The knowledge base must be:
- Non-redundant: No duplicate insights - always search before creating
- Self-consistent: Notes should not contradict each other without explicit acknowledgment
- Non-contradicting: When conflicts arise, resolve or document the tension explicitly
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.