Enforce single H1, heading order, and spacing in Markdown documents.
npx skills add https://github.com/ronniegeraghty/hyoka --skill markdown-headings
Please help me install this Agent Skill. Skill: markdown-headings Source: https://github.com/ronniegeraghty/hyoka/tree/main/skills/test/markdown-headings Command: npx skills add https://github.com/ronniegeraghty/hyoka --skill markdown-headings
This rule set ensures every markdown document uses a correct and consistent heading structure, preventing misformatted or ambiguous content.
Apply this rule to a new or existing Markdown document before saving to ensure correct heading hierarchy.
High-intent search queries and answers about installing and using this skill.
To enforce correct markdown heading structures, apply automated rules that restrict documents to a single H1 and ensure proper heading level progression. This guarantees accessible content by preventing misformatted or ambiguous heading hierarchies.
Correct markdown heading formatting requires exactly one H1 per document, proper level ordering, and appropriate blank lines around headings. Maintaining this structure prevents ambiguous content and ensures consistent formatting across files.
To add provenance markers for tracing markdown heading source and intent, insert a specific HTML comment marker immediately above the H1. This traces document source and intent, ensuring traceability across multiple markdown files.
Yes, this markdown heading validation works for existing guides and templates. You can apply these rules to existing documents before saving to check level progression and formatting, guaranteeing well-structured markdown content.
benjaminhaeberliGenerate and update structured Markdown documents with frontmatter metadata and footers.
tentacle-proConvert Obsidian-flavored markdown to HTML via an enterprise rendering API.
ivyFormat GitHub-flavored Markdown with correct headings, code blocks, links, and callouts.
baasith6Check and correct Markdown formatting errors in documentation files.
