markdown-plus-plus

Validate Markdown++ variables, conditions, includes, aliases, and markers.

1|Updated Dec 5, 2025

Search Tags:#documentation #validation #syntax #aliases #markers #includes #markdown++

Ready to run

npx skills add https://github.com/quadralay/webworks-claude-skills --skill markdown-plus-plus

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: markdown-plus-plus
Source: https://github.com/quadralay/webworks-claude-skills/tree/main/plugins/webworks-claude-skills/skills/markdown-plus-plus
Command: npx skills add https://github.com/quadralay/webworks-claude-skills --skill markdown-plus-plus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Markdown++ extends Markdown with variables, conditions, includes, styles, markers, and aliases, but authoring consistent, error-free documents is challenging.

Core Features & Use Cases

Audit and validate Markdown++ syntax across core extensions (variables, styles, conditions, includes, markers) to catch mistakes before publishing.
Detect duplicate aliases, invalid variable names, malformed JSON, and broken includes across documents.
Provide actionable guidance and examples to fix issues in real-world docs such as user guides or API references.

Quick Start

Analyze a Markdown++ file to identify syntax errors and generate actionable fixes.

Frequently Asked Questions about markdown-plus-plus

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

FAQPage Schema

How do I validate Markdown++ syntax for variables and includes?▼

To validate Markdown++ syntax, audit documents to identify invalid variable names, malformed JSON in markers, and broken includes, receiving actionable guidance to fix structural issues before publishing.

What causes circular include errors in Markdown++ documents?▼

Circular include errors in Markdown++ documents occur when file dependencies loop back on themselves, which validation detects by tracing include paths to ensure structural consistency across project files.

How do I fix malformed JSON in Markdown++ markers?▼

Fix malformed JSON in Markdown++ markers by auditing the syntax to detect formatting mistakes, then applying the provided remediation examples to correct the marker block structure.

Can I check for duplicate aliases across multiple Markdown++ files?▼

Yes, you can check for duplicate aliases across Markdown++ files by running a validation audit that detects naming collisions and provides clear remediation guidance to ensure consistent syntax.

Does Markdown++ validation work for API references and release notes?▼

Yes, Markdown++ validation works for API references and release notes, applying consistent syntax checks for variables, conditions, and markers across a wide range of technical documentation tasks.

What are the limitations of automated Markdown++ syntax checks?▼

Limitations of Markdown++ syntax checks include focusing on structural validation for markers and conditions, while requiring proper JSON formatting and not detecting logical errors in variable content.