manage-mdx-content

Enforce mandatory frontmatter and consistent structure for MDX articles.

Updated Dec 26, 2025
One-click install
npx skills add https://github.com/DeltaFoundry850/crispy-fishstick --skill manage-mdx-content-deltafoundry850
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-mdx-content
Source: https://github.com/DeltaFoundry850/crispy-fishstick/tree/main/.agent/skills/manage-mdx-content
Command: npx skills add https://github.com/DeltaFoundry850/crispy-fishstick --skill manage-mdx-content-deltafoundry850

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Content teams often struggle to maintain consistent MDX content across Work (case studies) and Insights (articles), leading to mismatched frontmatter, inconsistent structure, and brittle publishing pipelines.

Core Features & Use Cases

  • Enforces mandatory frontmatter fields (title, description, date) and recommended fields (tags, readTime, image) to ensure reliable rendering and SEO.
  • Provides a structured authoring workflow that guides writers from location selection to validation and rendering.
  • Supports standardized MDX formatting for Work and Insights, including reusable components and reference patterns.

Quick Start

Create a new MDX article in content/work or content/insights with complete frontmatter and the standardized structure.

Frequently Asked Questions about manage-mdx-content

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

FAQPage Schema
How do I enforce required frontmatter fields for MDX content?

To enforce required MDX frontmatter fields, apply content standards that mandate title, description, and date properties. This ensures reliable rendering and SEO for work and insights articles, preventing mismatched metadata and brittle publishing pipelines.

What is the standard MDX authoring workflow for case studies and insights articles?

The standard MDX authoring workflow guides writers from location selection through validation and rendering. It enforces consistent MDX structure and documented frontmatter fields for content stored in the work and insights directories.

Which frontmatter fields are mandatory versus recommended for MDX articles?

Mandatory MDX frontmatter fields include title, description, and date. Recommended metadata fields are tags, readTime, and image, which enhance SEO and content presentation without blocking the publishing workflow.

Can I use reusable components within my standardized MDX content structure?

Yes, standardized MDX formatting supports reusable components and reference patterns. This allows content authors and editors to maintain consistent structure across work and insights articles during creation and updates.

Why does my MDX content pipeline break when frontmatter is missing?

MDX publishing pipelines break when mandatory frontmatter fields like title, description, or date are missing because rendering engines expect reliable metadata. Enforcing strict content standards prevents these mismatches and ensures consistent structure.

What's the best way to maintain consistent MDX structure across multiple content authors?

The best way to maintain consistent MDX structure is to enforce documented authoring workflows and strict frontmatter validation. This ensures all content authors follow standardized formatting for work and insights articles from draft to publish.