obsidian-markdown-structure_skill

Overview

This skill validates and enforces consistent Markdown document structure for Obsidian vaults. It checks frontmatter placement, heading hierarchy, and content organization to ensure files follow a predictable template. Use it to catch structural problems early and keep notes uniform across a vault.

How this skill works

The skill inspects a Markdown file for a single YAML frontmatter block at the very top and requires a blank line after the closing ---. It checks that headings start at H2 for main sections, that subheadings follow H3/H4 without skipping levels, and that no content appears before the first heading. It also validates summary-first organization and correct blockquote attribution patterns.

When to use it

• When creating new Markdown documents to ensure they start with correct structure.
• When validating existing files to find frontmatter, heading, or organization issues.
• When preparing content for sharing or publishing from an Obsidian vault.
• When enforcing team or personal style standards across many notes.

Best practices

• Keep exactly one YAML frontmatter block at the top and add a blank line after it.
• Use H2 (##) for main sections, H3 (###) for subsections, and avoid skipping heading levels.
• Always include a Summary or Overview section as the first visible heading.
• Put no content before the first heading; avoid H1 headings that duplicate frontmatter title.
• Format quotes as blockquotes and include attribution on a separate line when possible.

Example use cases

• Batch-validate a vault to locate files with misplaced frontmatter or missing blank line.
• Standardize note templates so every document begins with a Summary and consistent headings.
• Prepare a set of documents for export by ensuring heading hierarchy and quote formatting are correct.
• Fix structural issues flagged by automated linters or CI checks before publishing.