vault-structure_skill

This skill helps you organize and reference your Obsidian vault layout, tagging, and templates for faster, accurate note placement.

Shell

1

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 kriscard/kriscard-claude-plugins --skill vault-structure

SKILL.md13.2 KB

Overview

This skill captures the exact Obsidian vault layout, tagging taxonomy, templates, and PARA decisions for /Users/kriscard/obsidian-vault-kriscard. It helps place new notes, pick templates, apply tags correctly, and follow inbox processing and maintenance routines. Use it whenever note placement, tagging, or vault-aware automation is required.

How this skill works

The skill inspects the vault's core folders (Inbox, Projects, Areas, Resources, Archives, MOCs) and the Templates folder, plus key org documents under 3 - Resources/Obsidian org/. It applies the PARA decision tree to recommend storage location and suggests subject tags, appropriate templates, and MOC/linking updates. It also enforces tagging rules (max 3–4, no folder-duplicates) and standard naming patterns for daily notes and OKRs.

When to use it

Creating a new note and deciding which PARA folder to use
Choosing the correct template for daily notes, projects, meetings, or OKRs
Tagging a note without duplicating folder context
Processing the Inbox to route notes weekly
Running vault maintenance or archiving tasks

Best practices

Follow the PARA decision tree: Projects → Areas → Resources → Inbox → Archives
Use only 1–2 subject tags plus optional status/flashcard tags (max 3–4 total)
Do not tag what the folder already indicates (avoid project/area/reference tags)
Use Templates/ for standard note types and Daily Notes.md for daily workflow
Create MOCs when a topic has 10+ notes and update them monthly

Example use cases

Create a new project: place under 1 - Projects/[Project Name]/, use Project Brief.md and tag with subject + #active
Daily workflow: auto-create YYYY-MM-DD.md in 2 - Areas/Daily Ops/ using Daily Notes.md, link to active projects and area notes
TIL capture: save to 3 - Resources/TIL/ and tag with til/<topic> like #til/react
Inbox processing: read entries in 0 - Inbox/, apply decision tree, add subject tags, link to MOCs, move to correct PARA folder
Archiving: move completed projects to 4 - Archives/Projects - YYYY/ and update MOCs and backlinks

FAQ

Place it in the most relevant Project or Area folder. Use Meeting Notes.md or 1-on-1 Meeting Notes.md and tag with a subject tag only (no meeting tag).

How many tags per note?

Prefer 1–2 subject tags plus optional status or flashcard tag. Keep total tags to 3–4 to avoid noise.

When do I create a MOC?

Create a MOC when a topic accumulates roughly 10+ related notes or when you need a navigational hub across PARA categories.