yaml-schema

Generate categorized Markdown solution files with validated YAML frontmatter.

47|11|Updated Nov 26, 2025
One-click install
npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill yaml-schema
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: yaml-schema
Source: https://github.com/majesticlabs-dev/majestic-marketplace/tree/main/plugins/majestic-engineer/skills/fix-reporter/references/yaml-schema.md
Command: npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill yaml-schema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This reference defines the YAML frontmatter schema used by fix-reporter outputs to guarantee consistent categorization and validation.

Core Features & Use Cases

  • Schema Validation: Ensures required fields and enum values are present.
  • Category Mapping: Guides where to store documentation.
  • Usage Examples: Shows valid metadata structures.

Quick Start

Review the schema.yaml and its example to validate your fix-report documents.

Frequently Asked Questions about yaml-schema

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

FAQPage Schema
How do I validate YAML frontmatter in my fix documentation?

YAML schema validation ensures your fix-report documents have required fields and correct enum values. The schema.yaml file defines the structure that categorizes and validates frontmatter metadata automatically when you generate documented solutions.

What YAML schema structure do fix-report documents need?

Fix-report documents require YAML frontmatter with categorized metadata fields defined by schema.yaml. This frontmatter guides file placement under docs/solutions by problem_type and enforces consistent field naming and allowed values across all fix documentation.

Can I use this schema to organize solved problems across multiple project modules?

Yes. The schema enables deterministic file organization by mapping problem categories to docs/solutions directories. Applying the schema after confirming solutions across modules ensures consistent categorization and fast lookup of previously solved non-trivial issues.

What happens if my YAML frontmatter doesn't match the schema?

Schema validation catches missing required fields and invalid enum values before documentation is generated. This prevents malformed fix-report files and ensures all categorized solutions meet the metadata structure needed for reliable lookup and consistency.

When should I document a fix using this schema?

Apply this schema after confirming a solution for non-trivial issues that required multiple investigation attempts or non-obvious fixes. The schema ensures these valuable solutions are consistently categorized and stored for future reference across your project.

How does schema-based categorization improve fix documentation?

The schema maps problem types to storage locations and enforces uniform metadata fields, making fixes discoverable and reproducible. Deterministic filenames and category placement under docs/solutions enable fast lookup when the same problems recur.

Related Skills