Verified:GitHub

obsidian-guidelines

Enforce Obsidian vault naming, linking, and folder conventions with sync detection.

1|Updated Dec 23, 2025

Search Tags:#note-taking #knowledge management #obsidian #naming conventions #sync workflow #vault guidelines #linking rules

Ready to run

npx skills add https://github.com/huangeddie/dotfiles --skill obsidian-guidelines

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: obsidian-guidelines
Source: https://github.com/huangeddie/dotfiles/tree/main/dot_agents/exact_packages/assistant/exact_skills/obsidian-guidelines
Command: npx skills add https://github.com/huangeddie/dotfiles --skill obsidian-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents your Obsidian vault from degrading into inconsistent file names, broken linking habits, and unclear folder structure by enforcing a bottom-up kepano-style writing convention.

Core Features & Use Cases

Vault-level sync compliance: Detects whether you sync via Obsidian CLI or git and instructs the correct sync steps before/after reads and writes.
Structured organization without folder bloat: Guides you to avoid folders for categorization and instead use Obsidian Base-style categories plus internal links.
Consistent naming and linking: Enforces date formats, pluralized tags/categories, and practices that ensure future search and navigation work well.
Violation flagging: When operating on the vault, it flags deviations, explains the correct convention, and suggests fixes while allowing user override.

Quick Start

Tell the agent to review or create an Obsidian note and apply the vault conventions, including sync steps, naming, folder rules, and link practices.

Frequently Asked Questions about obsidian-guidelines

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

FAQPage Schema

How do I keep my Obsidian vault naming conventions and linking rules consistent?▼

To keep your Obsidian vault consistent, enforce bottom-up kepano-style writing conventions for note-taking, applying strict date formats, pluralized tags, and internal links to ensure future search and navigation work well.

What is the best way to organize an Obsidian vault without creating folder bloat?▼

The best way to organize an Obsidian vault without folder bloat is to avoid folders for categorization and instead use Obsidian Base-style categories plus internal links for structured navigation.

How do I handle Obsidian sync workflow compliance using git or CLI?▼

Handle Obsidian sync workflow compliance by detecting whether you sync via Obsidian CLI or git, then instructing the correct sync steps to execute before and after reading or writing vault content.

Can I get violation flagging with suggested fixes for broken Obsidian vault guidelines?▼

Yes, you can get violation flagging with suggested fixes for broken Obsidian vault guidelines. When operating on the vault, deviations are flagged, correct conventions are explained, and fixes are suggested while allowing user override.

Does this approach work with daily notes, clippings, and reference material in Obsidian?▼

Yes, this approach works with daily notes, clippings, and reference material in Obsidian. It applies when you read, write, search, list, or operate on any vault content, including templates and clippings.