obsidian-vault

Enforce Obsidian vault structure, filename, frontmatter, and wikilinking rules.

Updated May 5, 2026
One-click install
npx skills add https://github.com/ethan-rio/skills --skill obsidian-vault-ethan-rio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-vault
Source: https://github.com/ethan-rio/skills/tree/main/skills/personal_agent/obsidian-vault
Command: npx skills add https://github.com/ethan-rio/skills --skill obsidian-vault-ethan-rio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates inconsistent Obsidian vault structure, broken wikilinks, and non-compliant note creation that disrupt personal agent knowledge management workflows, ensuring all notes follow a shared contract that other skills can rely on.

Core Features & Use Cases

  • Standardized Vault Contract: Defines a fixed folder layout (Inbox, Source, Wiki, Index), strict filename rules, and required YAML frontmatter fields for every note type.
  • Canonical Note Creation Helper: Includes the new_note.sh script, the only sanctioned way to create vault notes, which automatically enforces all naming, frontmatter, and linking rules to eliminate human error.
  • Cross-Skill Compatibility: Acts as the foundational contract for all other personal_agent skills, so ingest, curation, graph extraction, and recall tools all work with consistently formatted notes.
  • Use Case: If you run a personal agent that ingests YouTube videos, articles, and voice notes into Obsidian, this Skill ensures every captured note has the correct filename, frontmatter, and related links so you can search, curate, and synthesize content reliably.

Quick Start

Ask your agent to create a new inbox note for the article The Bitter Lesson from https://example.com/bitter-lesson with tags ai and scaling, and it will automatically generate a fully compliant note in your Obsidian vault.

Frequently Asked Questions about obsidian-vault

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

FAQPage Schema
How do I standardize Obsidian vault structure for personal agents?

Standardize Obsidian vault structure by enforcing a fixed folder layout, strict filename rules, and required YAML frontmatter fields. This ensures all notes follow a shared contract that personal agents can reliably ingest, curate, and query.

How do I enforce consistent frontmatter and wikilinking rules in Obsidian?

Enforce consistent frontmatter and wikilinking rules by using a canonical helper script to create notes. This automatically applies required YAML fields and cross-skill linking conventions to eliminate human error during note creation.

Why are broken wikilinks and non-compliant notes disrupting my knowledge management workflow?

Broken wikilinks and non-compliant notes disrupt knowledge management workflows because personal agents cannot reliably parse inconsistent formats. Applying a standardized vault contract ensures cross-skill compatibility for content capture and synthesis.

Can I use a personal agent to capture raw content into a standardized Obsidian vault?

Yes, you can capture raw content like YouTube videos and articles into a standardized Obsidian vault. The skill ensures every captured note receives the correct filename, frontmatter, and related links for reliable search and curation.

What is the best way to create compliant Obsidian notes for graph database integration?

The best way to create compliant notes for graph database integration is using the canonical helper script. It is the only sanctioned method for generating notes that satisfy the structural and frontmatter requirements needed for external graph extraction.

Do I need a fixed folder layout for my Obsidian personal knowledge management system?

You need a fixed folder layout with designated Inbox, Source, Wiki, and Index directories to maintain vault organization. This standardized structure allows personal agent skills to correctly locate, process, and synthesize ingested content.