obsidian-document-policy

Community

Enforce a unified Obsidian vault storage policy.

AuthorKIM-KYOUNG-OH
Version1.0.0
Installs0

System Documentation

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.

Dependency Matrix

Required Modules

None required

Components

Standard package

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: obsidian-document-policy
Download link: https://github.com/KIM-KYOUNG-OH/dotfiles/archive/main.zip#obsidian-document-policy

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 223,000+ vetted skills library on demand.