obsidian-document-policy

Define and enforce Obsidian vault storage and tagging policies.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/KIM-KYOUNG-OH/dotfiles --skill obsidian-document-policy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-document-policy
Source: https://github.com/KIM-KYOUNG-OH/dotfiles/tree/main/.claude/skills/obsidian-document-policy
Command: npx skills add https://github.com/KIM-KYOUNG-OH/dotfiles --skill obsidian-document-policy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Obsidian vaults often become disorganized as notes multiply across folders and types. This policy defines a clear structure for vault root locations, per-document type storage rules, and rigorous tagging to ensure consistency, discoverability, and governance across all Obsidian notes.

Core Features & Use Cases

  • Hierarchical tag system that enforces a consistent taxonomy for notes.
  • Document-type routing that maps notes to storage locations (000-SLIPBOX, 001-INBOX, 002-PROJECTS, 003-RESOURCES, archive).
  • Frontmatter conventions and file-naming rules to enable automated indexing and retrieval.
  • Exclusion rules to protect archive data and non-note artifacts from modification.
  • Use Case: A team standardizes notes for bug reports, QA, guides, and resources, enabling uniform search and cross-linking.

Quick Start

Apply the policy by annotating new notes with the required frontmatter and tags and placing them in the appropriate folders.

Frequently Asked Questions about obsidian-document-policy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize an Obsidian vault using a Zettelkasten folder structure?

You can organize an Obsidian vault by routing notes into specific folders like 000-SLIPBOX, 001-INBOX, 002-PROJECTS, 003-RESOURCES, and archive. This storage policy maps document types to correct paths for consistent retrieval.

What is the best way to enforce consistent tagging and frontmatter in Obsidian notes?

Enforcing consistent tagging and frontmatter requires applying a unified vault policy. It defines hierarchical tags and frontmatter conventions for every note, ensuring strict taxonomy, automated indexing, and reliable cross-linking across your documents.

How do I standardize file naming conventions and storage paths for Obsidian note management?

You can standardize file naming and storage paths by applying a reusable vault policy. It specifies exact routing rules for folders like 002-PROJECTS and 003-RESOURCES, ensuring notes are placed correctly and named uniformly for automated retrieval.

Can I protect archived notes and non-note artifacts from being modified in Obsidian?

Yes, you can protect archived data by applying exclusion rules within your vault policy. These rules specifically safeguard your archive folder and non-note artifacts from accidental modification while governing active note storage.

Does this Obsidian vault policy work for team note management and bug reporting?

Yes, this vault policy works for team note management by standardizing storage for bug reports, guides, and resources. Applying consistent frontmatter and hierarchical tags enables uniform search and cross-linking across all team documents.