Create a structured knowledge note in the Obsidian Ideaverse vault from any input — pasted text, rough notes, Notion exports, Apple Notes, OneNote content, clipboard dumps, meeting notes, or freeform context the user provides. Use this skill whenever the user wants to add knowledge to their vault, asks to "create a note", "save this", "add this to my knowledge base", imports content from another app, or provides raw information that should become a vault note. Also triggers when the user pastes a block of text and wants it structured, or says things like "turn this into a note", "clean this up for my vault", or "I learned something about X".
Transform any user-provided content into a properly structured Ideaverse vault note following ACE conventions.
| Input | How to handle |
|---|---|
| Pasted text / raw notes | Structure and distill directly |
| Notion export (markdown or plain text) | Strip Notion artifacts (database properties rendered as text, toggle syntax, etc.), restructure |
| Apple Notes paste | Clean up formatting (often loses structure), rebuild with headers |
| OneNote paste | Handle nested bullet madness, flatten and restructure |
| Meeting notes / transcript | Extract decisions, action items, key points |
| Freeform "I learned about X" | Research the topic if needed, build a proper knowledge note |
| Multiple fragments | Ask user if they want one combined note or separate notes |
Read the user's input carefully. Identify:
If anything is ambiguous, ask the user before proceeding. Common clarifying questions:
| Note type | Folder | Template basis |
|---|---|---|
| Concept / idea / knowledge | Atlas/Dots/ | Base template |
| Person | Atlas/Dots/People/ | Base template + person fields |
| Source (book, paper, video) | Atlas/Dots/ | Source template |
| Effort / project | Efforts/<intensity>/ | Effort template |
| Daily / timestamped | Calendar/ | Daily Note template |
| Quick capture / unprocessed | +/ | Minimal frontmatter |
Before assigning metadata, scan the vault for context:
Existing tags — Search frontmatter across the vault for tags. Reuse what fits. Only create 1-2 new tags if nothing existing covers the topic. Tags should be lowercase, hyphenated for multi-word.
Relevant MOCs — Read Atlas/Maps/Library.md for the LYT Classification System. Find the best-fit MOC(s) for the in property. If no MOC fits well, use the broadest parent and mention to the user that a new MOC might be warranted as this area grows.
Existing related notes — Search the vault for notes on similar topics. These become related links and [[wikilink]] candidates in the body.
Use the appropriate frontmatter template:
For knowledge notes (Dots):
---