Vault

Skill magnusrodseth/dotfiles/.claude/skills/vault

⚙️ There are many like them, but these dotfiles are mine. A stow-managed macOS setup: Zsh, Neovim, tmux, Ghostty, and a pile of Claude Code tooling.

Install

npx -y skills add magnusrodseth/dotfiles --skill vault

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

3.0 KB, as published. Nobody here has run it

Vault Knowledge Capture

Extract valuable insights from conversations and store them in the user's Obsidian vault.

Can be invoked from ANY project on the machine.

Configuration

Resolve the vault location first, then use $VAULT everywhere below:

if [ -d "$HOME/dev/personal/vault" ]; then
    VAULT="$HOME/dev/personal/vault"          # local machine (any cwd)
else
    VAULT="${CLAUDE_PROJECT_DIR:-$PWD}"       # cloud session: the repo IS the vault
fi

Expand $HOME to the user's actual home directory. The fallback matters in Claude Code cloud/web sessions, where the vault is cloned to a sandbox path and $HOME/dev/personal/vault does not exist. On a local machine the first branch always wins, so behaviour there is unchanged.

Workflow

Read $VAULT/CLAUDE.md for current vault rules
Analyze conversation for knowledge to capture
Classify content type: learning | how-to-guide | brag | decision | note | resource | person | project | meeting
Read relevant template from $VAULT/Templates/{Type}.md
Search vault for existing related notes to link to (glob/grep $VAULT)
Write note to $VAULT/{folder}/{Note Name}.md

Content Type to Folder

Type	Path
learning	`$VAULT/Learning/`
how-to-guide	`$VAULT/Reference/`
brag	`$VAULT/Personal/`
decision	`$VAULT/Personal/`
note	`$VAULT/Notes/`
resource	`$VAULT/Reference/`
person	`$VAULT/Personal/People/`
project	`$VAULT/Projects/`
meeting	`$VAULT/Meetings/`

Required Reading Before Acting

Read these in order before creating any note:

$VAULT/CLAUDE.md (always)
Relevant skills based on task:
- $VAULT/.claude/skills/vault-management/SKILL.md
- $VAULT/.claude/skills/obsidian-markdown/SKILL.md
- $VAULT/.claude/skills/dataview/SKILL.md
- $VAULT/.claude/skills/templater/SKILL.md
- $VAULT/.claude/skills/mermaid/SKILL.md
- $VAULT/.claude/skills/excalidraw/SKILL.md
- $VAULT/.claude/skills/advanced-tables/SKILL.md
- $VAULT/.claude/skills/json-canvas/SKILL.md
- $VAULT/.claude/skills/obsidian-bases/SKILL.md
- $VAULT/.claude/skills/omnisearch/SKILL.md
- $VAULT/.claude/skills/obsidian-git/SKILL.md

Rules

Use [[wiki links]] for internal references, never markdown links
Always include YAML frontmatter
Date format: display DD.MM.YYYY, filenames YYYY-MM-DD
File naming: Human Readable Name.md (title case with spaces)
One idea per note (atomic notes)
Link liberally to build the knowledge graph
Search vault before creating duplicates
Always read the source files first; they contain the current truth