obsidian-write-document

Create and update Obsidian Markdown documents with frontmatter and wikilinks.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/BreakerOfStems/claude-skills --skill obsidian-write-document
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-write-document
Source: https://github.com/BreakerOfStems/claude-skills/tree/main/skills/obsidian-write-document
Command: npx skills add https://github.com/BreakerOfStems/claude-skills --skill obsidian-write-document

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation and updating of Obsidian Markdown documents, ensuring consistent formatting, proper wikilinks, and adherence to vault conventions.

Core Features & Use Cases

  • Create New Documents: Generates new Markdown files with specified content, frontmatter, and structure.
  • Update Existing Documents: Appends new sections or completely replaces content in existing files.
  • Use Case: Automatically generate a new specification document for a feature, complete with frontmatter, sections, and links to related notes, based on a proposal.

Quick Start

Use the obsidian-write-document skill to create a new document at 'notes/meeting-notes.md' with the title 'Project Alpha Meeting' and content 'Discussed project milestones and next steps.'.

Frequently Asked Questions about obsidian-write-document

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

FAQPage Schema
How do I automate Obsidian Markdown document creation with frontmatter and wikilinks?

You can create new Obsidian Markdown documents by specifying a file path, title, and content. The system applies frontmatter standards, heading hierarchy, and proper wikilinks to ensure your knowledge management vault remains interconnected and consistently formatted.

What is the best way to update existing Markdown notes in an Obsidian vault?

Updating existing Markdown notes in an Obsidian vault is handled by appending new sections or replacing content entirely. This maintains vault conventions and source attribution without disrupting the established document structure.

Does this approach to knowledge management support wikilinks for interconnected notes?

Wikilinks for interconnected notes are fully supported and enforced during document generation. This ensures new or updated Markdown files properly reference related notes, maintaining a well-organized and interconnected digital vault structure.

Can I generate a new specification document with sections and links based on a proposal?

Generating a new specification document from a proposal is a supported use case. The process creates a complete Markdown file with required frontmatter, structured sections, and links to related notes based on the provided proposal content.

What are the limitations of automating Obsidian document formatting?

Automating Obsidian document formatting requires strict adherence to frontmatter standards and source attribution for canonical documents. Limitations arise if the input content lacks the necessary structure or metadata required to enforce consistent vault conventions.