setup-vault-types

Solid

Use when configuring which document types a vault tracks: after installing ai-brain-starter, when a new kind of note appears (journals, books, meetings, clients, podcasts, travel, WhatsApp/Slack/iMessage exports), when extraction skips files because no extractor matches their type, or to add, list, or remove a custom type. Triggers: /setup-vault-types, "set up vault types", "add a note type", "enable an extractor". NOT for running extraction (use /second-brain-mapping).

AI & Automation 36 stars 35 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
52
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# /setup-vault-types > **`{SKILL_DIR}`** = this skill's own folder (locally: the directory this SKILL.md lives in; a served brain substitutes the real absolute path before you read this). Shared starter files live at the repo root two levels up: `{SKILL_DIR}/../..`. If a path does not resolve, name the missing file and stop — never guess another location. Figure out which doc types belong in this vault, then wire the right extractors. ## Why `/second-brain-mapping` ships with 18 extractors. You probably don't need all of them. This wizard: 1. Asks what kinds of notes you take 2. Enables the matching extractors 3. Offers to scaffold new extractors for types we don't ship No "start small" suggestion. You get all the capability for the types you have. ## Steps ### Step 1 — Detect existing types Scan the vault for files already declaring `type:` in frontmatter: ```bash cd "$(vault-root)" grep -rh "^type:" --include="*.md" -I . 2>/dev/null \ | sed 's/^type:\s*//' | sort | uniq -c | sort -rn | head -30 ``` Tell the user: *"Your vault already has these types declared: …"* ### Step 2 — Ask what they take notes on Present this list, ask user to pick any/all that apply: ``` Core journaling & reflection: [ ] journal — daily reflection / gratitude / mood [ ] daily_log — task-log style (Roam/Capacities daily) [ ] goal — OKRs, quarterly plans, vision docs Reading & learning: [ ] book — book notes, highlights, reviews [ ] article ...

Details

Author
mycelium-hq
Repository
mycelium-hq/ai-brain-starter
Created
5 months ago
Last Updated
yesterday
Language
Python
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

second-brain-mapping

Use when the user wants to map or remap their second brain, refresh the vault's queryable metadata index, extract structured frontmatter from typed notes (books, meetings, people, journals, goals), fill wikilink gaps, or surface cross-type insights and patterns no single file shows. Triggers: /second-brain-mapping, "map my second brain", "make my vault queryable", "refresh vault metadata", stale or sparse Dataview fields. Not for single-file reads or querying an existing graph (use graphify).

36 Updated yesterday
mycelium-hq
AI & Automation Listed

vault

Extract insights from conversations and store them in your Obsidian vault. Use when you want to capture learnings, how-to guides, brags, decisions, or any knowledge from the current chat into your second brain. Triggers on "save to vault", "store this in obsidian", "capture this learning", "add to vault", "remember this in obsidian", or any request to persist knowledge to the Obsidian vault.

2 Updated yesterday
magnusrodseth
AI & Automation Listed

vault-system

Use when maintaining the vault ITSELF as a system, not its content: knowledge-graph build/rebuild/query (graphify), second-brain mapping, vault diagnose/audit/hygiene, drift detection, extract rules from vault, backfill journals, setup vault types, consolidate memory (index over cap), Obsidian tooling (CLI/Bases/Markdown/JSON Canvas), vault bloat or Obsidian slow. Answering questions FROM the graph, use graph-query tools; daily journal/coaching/pattern detection, use those skills.

36 Updated yesterday
mycelium-hq