content-formatting

Enforce consistent frontmatter and header formatting across Lithos documentation pages.

24|2|Updated Feb 3, 2026

Search Tags:#linting #documentation #markdown #formatting #frontmatter #title-handling #yaml-escape

Ready to run

npx skills add https://github.com/jwintz/lithos --skill content-formatting

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: content-formatting
Source: https://github.com/jwintz/lithos/tree/main/skills/content-formatting
Command: npx skills add https://github.com/jwintz/lithos --skill content-formatting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lithos docs often suffer from inconsistent formatting and frontmatter issues that lead to rendering issues and confusion. This Skill documents Lithos formatting conventions to ensure consistent, predictable behavior across pages.

Core Features & Use Cases

Title Handling: Ensures the page title is sourced from the frontmatter title and avoids duplication when a title appears in the content.
Frontmatter Requirements: Recommends a minimum frontmatter block with title and description for every page.
Headers & Special Characters: Provides guidelines for section headers and escaping characters in YAML to prevent parsing errors.

Quick Start

Follow these steps to align a page with the formatting rules:

Add a frontmatter block with at least a title and description.
Ensure the content's main title comes from frontmatter and remove a duplicate title in the body.
Use proper section headers (## for H2, ### for H3) and escape special characters in YAML fields like colon: title: "My: Title" and quotes: title: 'He said "hello"'

Frequently Asked Questions about content-formatting

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

FAQPage Schema

How do I escape special characters in YAML frontmatter?▼

To escape special characters in YAML frontmatter, wrap values in quotes: use double quotes for colons like title: "My: Title" and single quotes for internal quotes like title: 'He said "hello"' to prevent parsing errors.

Why does my markdown documentation have duplicate titles?▼

Duplicate titles in markdown documentation occur when the title appears in both frontmatter and the page body. You should source the title exclusively from frontmatter and remove the duplicate title from the body content.

What frontmatter is required for markdown documentation pages?▼

Required frontmatter for markdown documentation pages includes a minimum block with both a title and a description. Adding this frontmatter ensures consistent rendering and predictable behavior across your pages.

How do I structure markdown headers for documentation?▼

To structure markdown headers for documentation, use proper section headers: ## for H2 and ### for H3. Consistent header structure ensures predictable formatting and prevents rendering issues across your pages.

What causes YAML parsing errors in markdown frontmatter?▼

YAML parsing errors in markdown frontmatter are caused by unescaped special characters like colons and quotes. Escaping characters by wrapping values in quotes prevents these parsing and rendering issues.

Does markdown linting apply to existing documentation pages?▼

Markdown linting applies to both new and existing documentation pages by validating frontmatter presence, title source, header structure, and escaping of special characters to enforce consistent content formatting.