managing-claude-docs

Centralize Claude documentation in an Obsidian vault with YAML frontmatter.

5|1|Updated Sep 6, 2009
One-click install
npx skills add https://github.com/bnadlerjr/dotfiles --skill managing-claude-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: managing-claude-docs
Source: https://github.com/bnadlerjr/dotfiles/tree/main/claude/skills/managing-claude-docs
Command: npx skills add https://github.com/bnadlerjr/dotfiles --skill managing-claude-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes Claude documentation in an Obsidian vault, consolidating plans, research, tickets, architecture, and handoffs to remove scattered notes.

Core Features & Use Cases

  • Central documentation home for Claude workflows.
  • Enforces consistent frontmatter structure and metadata across documents.
  • Supports templates for research and plans to speed up documentation.

Quick Start

Create a new Claude document under the appropriate Obsidian vault path and fill in the required frontmatter.

Frequently Asked Questions about managing-claude-docs

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

FAQPage Schema
How do I organize Claude documentation in an Obsidian vault?

To manage Claude documentation in Obsidian, create a new document under the appropriate vault path and fill in the required YAML frontmatter. You must include at least the name and description fields to maintain consistent metadata across your vault.

What is the required YAML frontmatter structure for Claude docs?

YAML frontmatter for Claude documents requires name and description fields at minimum. This standardizes metadata across the Obsidian vault, ensuring that plans, research, tickets, architecture, and handoffs remain consistently structured and searchable.

Can I use Obsidian templates for Claude research and plans?

Yes, templates are supported for research and plans to speed up Claude documentation creation. Applying templates in your Obsidian vault ensures the required YAML frontmatter and consistent structure are automatically populated for each new document.

What's the best way to centralize scattered Claude notes and handoffs?

Centralize scattered Claude notes by consolidating plans, research, tickets, architecture, and handoffs into a single Obsidian vault. This enforces consistent YAML frontmatter metadata across all documents, eliminating the fragmentation of scattered notes.

Do I need specific directories to manage Claude docs in Obsidian?

Specific directories are not strictly required, but the system supports optional directories for extended guidance. The only mandatory requirement is adding name and description fields to the YAML frontmatter of each Claude document in your Obsidian vault.

Why does my Claude documentation workflow lack consistent structure?

Your Claude documentation lacks consistent structure because it is missing standardized YAML frontmatter. Centralizing documents in an Obsidian vault and enforcing required name and description metadata fields resolves this structural inconsistency.