Advanced Markdown/MDX Processing

VerifiedCaution

Advanced Markdown and MDX processing for technical documentation. Parse, validate, lint, and transform Markdown content with support for MDX components, front matter, and remark/rehype plugins.

Sby Skills Guide Bot
DocumentationAdvanced
8/6/2026
Claude Code
#markdown#mdx#linting#documentation#frontmatter

Recommended for

Automated summary

This skill performs advanced Markdown and MDX processing: linting, validation, transformation, front matter parsing, and remark/rehype plugin configuration for technical documentation.

Strengths

  • Supports CommonMark, GFM, and MDX patterns including custom components and exports.
  • Provides structured lint and front matter outputs with detailed issues and severity levels.
  • Handles conversion between documentation formats and generation of tables and links.
  • Configurable via markdownlint config, JSON schemas, and remark/rehype plugins.

Limitations

  • Requires explicit input parameters; no automatic project detection is mentioned.
  • Advanced MDX processing may depend on external component libraries or plugins not included.
  • Focused on Markdown-family formats; not a general-purpose document conversion tool.
When to use it

Use this skill when you need to lint, validate, or convert Markdown/MDX files, or build reusable MDX documentation components.

When not to use it

Do not use it for non-Markdown formats (PDF, DOCX) or for full site rendering.

Security analysis

Caution
Quality score90/100

The skill uses Bash to run linting and transformation tools, which is legitimate for document processing but carries some risk if input is maliciously crafted. No explicit harmful instructions.

Findings
  • •Uses Bash tool, which could potentially execute commands if user input is not properly sanitized, but the skill itself only describes Markdown processing tasks.
How this analysis is made

Examples

Lint documentation folder
Lint all Markdown files in ./docs using the .markdownlint.json config and show me a summary of errors with fixes.
Validate front matter
Parse and validate front matter in docs/api/users.md against the schema in frontmatter.schema.json, and report if it is valid.
Transform Markdown to MDX with components
Convert my legacy .md files in ./guides to MDX and wrap code blocks in a custom CodeBlock component using remark/rehype plugins.

name: markdown-mdx description: Advanced Markdown and MDX processing for technical documentation. Parse, validate, lint, and transform Markdown content with support for MDX components, front matter, and remark/rehype plugins. allowed-tools: Read, Write, Edit, Bash, Glob, Grep backlog-id: SK-005 metadata: author: babysitter-sdk version: "1.0.0"

Markdown/MDX Skill

Advanced Markdown and MDX processing for technical documentation.

Capabilities

  • Parse and validate Markdown syntax (CommonMark, GFM)
  • MDX component development and integration
  • Remark/Rehype plugin configuration
  • Front matter parsing and validation
  • Markdown linting (markdownlint rules)
  • Table formatting and generation
  • Link validation and URL checking
  • Convert between documentation formats

Usage

Invoke this skill when you need to:

  • Lint and validate Markdown files
  • Create or integrate MDX components
  • Configure remark/rehype pipelines
  • Validate front matter schemas
  • Convert between documentation formats

Inputs

| Parameter | Type | Required | Description | |-----------|------|----------|-------------| | inputPath | string | Yes | Path to Markdown/MDX file or directory | | action | string | Yes | lint, validate, transform, parse-frontmatter | | outputPath | string | No | Output path for transformed content | | configPath | string | No | Path to markdownlint config | | frontmatterSchema | object | No | JSON schema for front matter validation | | plugins | array | No | Remark/rehype plugins to apply |

Input Example

{
  "inputPath": "./docs",
  "action": "lint",
  "configPath": ".markdownlint.json"
}

Output Structure

Lint Output

{
  "files": 42,
  "errors": 5,
  "warnings": 12,
  "issues": [
    {
      "file": "docs/getting-started.md",
      "line": 15,
      "rule": "MD022",
      "message": "Headings should be surrounded by blank lines",
      "severity": "error"
    }
  ],
  "fixable": 8
}

Front Matter Parse Output

{
  "file": "docs/api/users.md",
  "frontmatter": {
    "title": "Users API",
    "description": "User management endpoints",
    "tags": ["api", "users"],
    "sidebar_position": 3
  },
  "valid": true,
  "content": "# Users API\n\nThis document..."
}

Markdown Patterns

CommonMark Extensions

# Heading 1

## Heading 2 {#custom-id}

Paragraph with **bold**, *italic*, and `code`.

> Blockquote with
> multiple lines

- Unordered list
- With items
  - Nested item

1. Ordered list
2. With numbers

| Column 1 | Column 2 |
|----------|----------|
| Cell 1   | Cell 2   |

[Link text](https://example.com "Title")

![Alt text](image.png)

```javascript
const code = 'block';

Horizontal rule above.


### GitHub Flavored Markdown (GFM)

```markdown
## GFM Extensions

### Task Lists
- [x] Completed task
- [ ] Incomplete task

### Tables
| Left | Center | Right |
|:-----|:------:|------:|
| L    |   C    |     R |

### Strikethrough
~~deleted text~~

### Autolinks
https://example.com

### Footnotes
Here's a sentence with a footnote[^1].

[^1]: This is the footnote.

### Alerts
> [!NOTE]
> Useful information.

> [!WARNING]
> Critical content.

MDX Patterns

MDX Components

---
title: Interactive Guide
---

import { Tabs, TabItem } from '@site/src/components/Tabs';
import CodeBlock from '@theme/CodeBlock';

# Getting Started

<Tabs>
  <TabItem value="npm" label="npm">
    ```bash
    npm install my-package
    ```
  </TabItem>
  <TabItem value="yarn" label="yarn">
    ```bash
    yarn add my-package
    ```
  </TabItem>
</Tabs>

## Configuration

<CodeBlock language="json" title="config.json">
{`{
  "setting": "value"
}`}
</CodeBlock>

export const Highlight = ({children, color}) => (
  <span style={{backgroundColor: color, padding: '0.2rem'}}>
    {children}
  </span>
);

This is <Highlight color="#25c2a0">highlighted text</Highlight>.

MDX Component Library

// components/Callout.jsx
export function Callout({ type = 'info', title, children }) {
  const styles = {
    info: { bg: '#e7f5ff', border: '#339af0' },
    warning: { bg: '#fff3bf', border: '#fab005' },
    error: { bg: '#ffe3e3', border: '#fa5252' },
    success: { bg: '#d3f9d8', border: '#40c057' }
  };

  return (
    <div style={{
      backgroundColor: styles[type].bg,
      borderLeft: `4px solid ${styles[type].border}`,
      padding: '1rem',
      margin: '1rem 0'
    }}>
      {title && <strong>{title}</strong>}
      {children}
    </div>
  );
}
import { Callout } from '@site/src/components/Callout';

<Callout type="warning" title="Deprecation Notice">
  This API will be removed in version 3.0.
</Callout>

Markdownlint Configuration

.markdownlint.json

{
  "default": true,
  "MD013": false,
  "MD033": {
    "allowed_elements": ["details", "summary", "Tabs", "TabItem"]
  },
  "MD041": false,
  "MD024": {
    "siblings_only": true
  },
  "MD046": {
    "style": "fenced"
  },
  "MD048": {
    "style": "backtick"
  }
}

markdownlint-cli2 Configuration

# .markdownlint-cli2.yaml
config:
  default: true
  MD013: false

globs:
  - "docs/**/*.md"
  - "!node_modules"
  - "!.git"

ignores:
  - "CHANGELOG.md"

customRules:
  - markdownlint-rule-search-replace

Remark/Rehype Plugins

remark.config.mjs

import remarkGfm from 'remark-gfm';
import remarkFrontmatter from 'remark-frontmatter';
import remarkMdxFrontmatter from 'remark-mdx-frontmatter';
import remarkToc from 'remark-toc';
import remarkSlug from 'remark-slug';

export default {
  plugins: [
    remarkGfm,
    remarkFrontmatter,
    remarkMdxFrontmatter,
    [remarkToc, { heading: 'contents', tight: true }],
    remarkSlug
  ]
};

rehype.config.mjs

import rehypeSlug from 'rehype-slug';
import rehypeAutolinkHeadings from 'rehype-autolink-headings';
import rehypePrism from 'rehype-prism-plus';

export default {
  plugins: [
    rehypeSlug,
    [rehypeAutolinkHeadings, { behavior: 'wrap' }],
    [rehypePrism, { showLineNumbers: true }]
  ]
};

Front Matter Schema

JSON Schema for Validation

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "required": ["title"],
  "properties": {
    "title": {
      "type": "string",
      "minLength": 1,
      "maxLength": 100
    },
    "description": {
      "type": "string",
      "maxLength": 300
    },
    "tags": {
      "type": "array",
      "items": { "type": "string" }
    },
    "sidebar_position": {
      "type": "integer",
      "minimum": 0
    },
    "draft": {
      "type": "boolean",
      "default": false
    }
  },
  "additionalProperties": false
}

Workflow

  1. Parse content - Load Markdown/MDX files
  2. Extract front matter - Parse YAML front matter
  3. Validate structure - Check against schema
  4. Lint content - Apply markdownlint rules
  5. Transform - Apply remark/rehype plugins
  6. Report findings - Output validation results

Dependencies

{
  "devDependencies": {
    "markdownlint-cli2": "^0.12.0",
    "remark": "^15.0.0",
    "remark-gfm": "^4.0.0",
    "remark-frontmatter": "^5.0.0",
    "remark-mdx": "^3.0.0",
    "rehype": "^13.0.0",
    "gray-matter": "^4.0.0",
    "ajv": "^8.0.0"
  }
}

CLI Commands

# Lint all Markdown files
npx markdownlint-cli2 "docs/**/*.md"

# Fix auto-fixable issues
npx markdownlint-cli2 --fix "docs/**/*.md"

# Parse and validate front matter
node scripts/validate-frontmatter.js docs/

# Convert Markdown to HTML
npx remark docs/guide.md -o build/guide.html

Best Practices Applied

  • Use ATX-style headings (#)
  • Consistent list markers (- for unordered)
  • Fenced code blocks with language identifier
  • Front matter for metadata
  • Descriptive link text (not "click here")
  • Alt text for all images
  • One sentence per line for better diffs

References

  • CommonMark: https://commonmark.org/
  • GFM: https://github.github.com/gfm/
  • MDX: https://mdxjs.com/
  • markdownlint: https://github.com/DavidAnson/markdownlint
  • remark: https://remark.js.org/
  • rehype: https://github.com/rehypejs/rehype

Target Processes

  • style-guide-enforcement.js
  • docs-testing.js
  • docs-audit.js
  • content-strategy.js

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/advanced-markdown-mdx-processing-msh3ut3z/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/advanced-markdown-mdx-processing-msh3ut3z' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/advanced-markdown-mdx-processing-msh3ut3z/download' --output '.skill-downloads/advanced-markdown-mdx-processing-msh3ut3z/SKILL.md.part' && mv '.skill-downloads/advanced-markdown-mdx-processing-msh3ut3z/SKILL.md.part' '.skill-downloads/advanced-markdown-mdx-processing-msh3ut3z/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, Write, Edit, Bash, Glob, Grep

Original excerpt: Dependencies
{
  "devDependencies": {
    "markdownlint-cli2": "^0.12.0",
    "remark": "^15.0.0",
    "remark-gfm": "^4.0.0",
    "remark-frontmatter": "^5.0.0",
    "remark-mdx": "^3.0.0",
    "rehype": "^13.0.0",
    "gray-matter": "^4.0.0",
    "ajv": "^8.0.0"
  }
}

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/advanced-markdown-mdx-processing-msh3ut3z/SKILL.md' && test -s '.skill-downloads/advanced-markdown-mdx-processing-msh3ut3z/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/markdown-mdx' && cp -R '.skill-downloads/advanced-markdown-mdx-processing-msh3ut3z' '.claude/skills/markdown-mdx'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/advanced-markdown-mdx-processing-msh3ut3z'

openskills read 'advanced-markdown-mdx-processing-msh3ut3z'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/advanced-markdown-mdx-processing-msh3ut3z/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills