md-workflow

Create, edit, and lint Markdown files with YAML frontmatter awareness.

Updated Dec 28, 2025
One-click install
npx skills add https://github.com/ddttom/invisible-users --skill md-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: md-workflow
Source: https://github.com/ddttom/invisible-users/tree/main/.claude/skills/md-workflow
Command: npx skills add https://github.com/ddttom/invisible-users --skill md-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a complete workflow for creating, editing, and linting Markdown files with YAML frontmatter awareness, reducing formatting errors and speeding up documentation tasks.

Core Features & Use Cases

  • Create: Set up new Markdown files with proper YAML frontmatter structure and headings.
  • Edit: Modify existing Markdown with correct patterns and maintain frontmatter integrity.
  • Lint: Validate and auto-fix Markdown formatting according to configured rules.
  • YAML Frontmatter: Enforce best practices for frontmatter structure, including pattern choices to avoid MD025 duplicates.
  • Use Case: A documentation team wants to publish consistent Markdown posts across a repo with validated frontmatter.

Quick Start

Use the md-workflow command to initialize and lint a sample Markdown file in your project. For example: Create a new file docs/sample.md with frontmatter and an H1 in content and run the lint steps described in the Quick Reference.

Frequently Asked Questions about md-workflow

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

FAQPage Schema
How do I lint Markdown files and enforce YAML frontmatter patterns?

To lint Markdown files and enforce YAML frontmatter patterns, use this skill to validate formatting, auto-fix errors, and apply frontmatter structure rules to maintain documentation consistency across a repository.

How do I prevent duplicate H1 headings when adding YAML frontmatter to Markdown?

To prevent duplicate H1 headings when adding YAML frontmatter to Markdown, this skill enforces specific frontmatter pattern choices and heading placement rules to avoid MD025 linting violations.

What is the best way to create new Markdown files with consistent frontmatter for a documentation team?

The best way to create new Markdown files with consistent frontmatter is using an automated workflow that initializes documents with proper YAML structure and headings, ensuring repository-wide standards for content teams.

Can I edit existing Markdown documents without breaking the frontmatter structure?

Yes, you can edit existing Markdown documents without breaking frontmatter structure because this skill modifies content using correct patterns while maintaining YAML frontmatter integrity during documentation updates.

Does this Markdown linting workflow require any external dependencies?

No, this Markdown linting workflow does not require external dependencies, allowing content teams to directly validate and auto-fix Markdown formatting and frontmatter structure without additional environment setup.

Why should I use a Markdown workflow for repository-wide documentation standards?

You should use a Markdown workflow for repository-wide documentation standards because it reduces formatting errors, speeds up documentation tasks, and enforces consistent linting rules and frontmatter patterns across all files.