Menu
Analyze conversation for learnings and save to docs folder
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Must read guide on creating/editing mermaid charts with validation tools and syntax reference for all diagram types
Generate interactive HTML walkthroughs with clickable Mermaid diagrams (flowcharts and ER diagrams) that explain codebase features, flows, architecture, and database schemas. Use when asked to "walkthrough", "explain this flow", "how does X work", "trace the code path", "annotated diagram", "code walkthrough", "explain the architecture of", "walk me through", "database schema", "explain the tables", "data model".
Create a note from any resource: URL, book, podcast, article, video, GitHub repo, Reddit thread, PDF, quote, or raw idea. Trigger on "add", "save", "capture", "note this", "take notes on", or any request to record content in the knowledge base.
Add tweets to the Second Brain. Use when the user provides a Twitter/X URL and pasted tweet content, asking to "add a tweet", "save this tweet", or "capture this tweet".
Query your Second Brain with keyword search. Use when asked to "ask my notes", "what do I know about", "query my knowledge", "/ask", or when the user has a question that their notes might answer.
Create Obsidian templates for the Second Brain vault. Use when asked to "create a template", "make a template for", "add an Obsidian template", or "template for X".
| name | learn |
| description | Analyze conversation for learnings and save to docs folder |
| argument-hint | ["optional topic hint"] |
| model | claude-opus-4-5-20251101 |
| allowed-tools | Read, Write, Edit, Glob, Grep, AskUserQuestion |
Analyze this conversation for insights worth preserving in the project's documentation.
If a topic hint was provided via $ARGUMENTS, focus on capturing that specific learning.
If no hint provided, analyze the full conversation for valuable insights.
Think deeply about what was learned in this conversation:
Only capture insights that are:
If nothing valuable was learned, say so and exit gracefully.
Read existing docs to find the best home. Look for a docs/ folder or similar documentation directory in the project.
If no existing doc fits, propose a new doc file with kebab-case naming.
Note: CLAUDE.md stays stable as the entry point. All detailed learnings go to /docs only.
Format the insight to match existing doc style:
Present your proposed changes:
Wait for explicit user approval before saving.
After approval, save the learning and confirm what was captured.
