obsidian-notes-skilllisted

Create, convert, or reformat notes in the user's Obsidian vault to match THEIR OWN structure. The skill learns each vault once through a setup wizard and saves the layout (folder roles, tag style, date format, promotion style) to vault-config.yaml. Use whenever the user asks to make an "obsidian note", "main note", "atomic note", "zettelkasten note", "source note", "convert this to my structure", "add to my vault", "file this in obsidian", clean up a note's frontmatter/tags, or set up / change how notes are filed. Also trigger when the user pastes rough content and asks to file it into Obsidian, or points at a note in the vault and asks to normalize/restructure it. Works with any vault layout — Zettelkasten, PARA, flat, or custom.
kaushikhegde11/obsidian-notes-skill · ★ 0 · Data & Documents · score 58

Install: claude install-skill kaushikhegde11/obsidian-notes-skill

# Obsidian Notes File and format notes into the user's Obsidian vault. Every vault is different, so this skill **does not assume a fixed layout**. It reads the user's structure from a config file and follows it. It learns that structure once, through a setup wizard, then reuses it. The Zettelkasten ideas below (atomic notes, own words, interlinking) are **guidance**, not requirements. A user's config decides the actual folders and conventions. ## Config file location The user's saved config lives at **`~/.claude/obsidian-notes-vault-config.yaml`** (expand `~` to the user's home dir). Call this path `<CONFIG>` below. It is kept outside this skill's folder on purpose: this skill may be installed as a plugin under a read-only or auto-updated directory, so writing config next to `SKILL.md` is not safe. Always read and write `<CONFIG>` at the home path. Migration: if `<CONFIG>` does not exist but a legacy `vault-config.yaml` sits next to `SKILL.md`, copy that legacy file to `<CONFIG>` once, then use `<CONFIG>` from then on. ## Step 1 — Load config or run setup (always first) Read `<CONFIG>` (`~/.claude/obsidian-notes-vault-config.yaml`). - If the file exists and has a `vault_root` and a `folders` block → **load it**. Use its values for everything below. Do not run the wizard. - If the file is missing or incomplete → **run the Setup wizard** (next section), write the file, then continue. `vault-config.example.yaml` (in this skill's own folder, next to `SKILL.md`) documents