obsidian-note-formatting-skill

What problem does it solve?

Many users struggle to create consistent, well-structured Obsidian notes with valid YAML frontmatter, clear filenames, and proper internal linking, which makes knowledge retrieval and vault organization unreliable. This skill removes friction by producing Obsidian-compatible markdown that follows naming, tagging, and folder conventions and by validating frontmatter before saving. It also guides users through folder placement and related-note discovery so notes land in the right place and connect to existing content.

Core Features & Use Cases

• Structured Frontmatter Generation: Automatically produce YAML frontmatter with date, status, type, and relevant tags that meet validation rules.
• Template Application & Formatting: Apply templates for technical notes, ideas, meetings, literature, and learning notes to ensure consistent headings and sections.
• Vault-aware Suggestions & Saving: Suggest folder placement using a decision tree, discover related notes via Obsidian MCP search, format wikilinks, and optionally save the note to the user's vault using MCP after explicit confirmation.
• Validation & Guidance: Run frontmatter and content checks (via provided validator) and present warnings for title length, tag format, and missing headings to improve note quality.

Quick Start

Create an Obsidian note titled Project Launch Plan using a technical template, include YAML frontmatter with date, status, type and at least two tags, suggest a folder and related notes, then ask me if you should save it to my vault.