5
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill mrfelton/ideaverse --skill ideaverse-enrichment- SKILL.md9.0 KB
Overview
This skill systematically enriches Ideaverse vaults using the ARC workflow: Add → Relate → Communicate. It captures new knowledge quickly, classifies and integrates it into existing structures, and ensures consistency by detecting duplicates and validating links. Use it to assimilate articles, research, experiences, or any incoming ideas into a coherent vault.
How this skill works
On request, the skill captures raw input quickly into an appropriate container (daily log, fleeting note, or Atlas). It then searches the vault for existing coverage, classifies the knowledge type (concept, process, entity, principle), extracts atomic notes, links them into MOCs, and validates frontmatter and links. Finally, it records that enrichment happened and surfaces the new or updated notes for use in projects and logs.
When to use it
- When adding an article, book chapter, or research paper to your vault
- When processing an experience or personal observation into reusable insights
- When integrating multiple sources into a topic-level synthesis
- When you need to classify a piece of knowledge or decide its note type
- When checking for duplicates or consolidating similar notes
Best practices
- Capture fast: prioritize getting the idea into the system before organizing
- Search before creating: always check for exact matches, synonyms, and semantic overlaps
- Extract atomic notes: one distinct idea per note with clear frontmatter
- Link deliberately: add property-to-MOC and related links, then validate them
- Prefer incremental enrichment: small, regular updates beat large one-off imports
Example use cases
- Process a blog post: capture key points, extract 2–5 concepts, add notes and link to source MOC
- Integrate research: synthesize findings into a temporary note, identify gaps, create atomic notes to fill them
- Turn an experience into a principle: extract a generalizable heuristic and link it to the experience log
- De-duplicate notes: detect synonyms, merge content into a primary note, update links and MOCs
- Document a process: convert a how-to into a stepwise process note with decision points and failure modes
FAQ
It runs exact and synonym searches, reviews relevant MOCs, and performs a semantic scan. If the new info supplements an existing note it updates; if it’s truly distinct it creates a new atomic note. When unsure it creates a flagged note for later dedup review.
What metadata is required for each extracted note?
Each note should include source attribution and frontmatter with at least up: (parent/MOC) and created:. Related links and a clear type classification are recommended.