schema

Generate categorized Markdown solution files with YAML frontmatter and schema validation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This schema enforces required fields, enums, and validation rules for fix-reporter outputs.

Core Features & Use Cases

  • Required Fields: Ensure module, date, problem_type, etc.
  • Enum Validation: Enforce allowed values for each field.
  • Category Mapping: Aligns reports with docs paths.

Quick Start

Validate a sample fix report against the schema to ensure compliance.

Frequently Asked Questions about schema

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

FAQPage Schema
How do I validate YAML metadata against a schema?

YAML schema validation enforces required fields, enums, and rules defined in schema.yaml. This Skill automatically validates fix-report outputs against your schema to ensure all metadata meets compliance requirements before documentation is generated.

What fields are required in a fix-report for documentation?

Required fields include module, date, and problem_type, enforced by schema validation. The Skill rejects incomplete reports and ensures every documented solution carries consistent, queryable metadata across your docs repository.

How does the schema organize solved problems into documentation?

The schema maps problem reports to category directories and generates sanitized filenames (symptom-module-YYYYMMDD.md) with YAML frontmatter. This creates a structured, indexed documentation library where each solution is stored under docs/solutions/[category]/ for fast lookup.

Can I enforce specific values for metadata fields in my documentation?

Yes, enum validation within the schema restricts each field to allowed values. This prevents inconsistent problem classifications and ensures downstream tools can reliably parse and categorize your documented fixes.

What happens if a fix-report doesn't match the schema?

Schema validation rejects non-compliant reports before they generate documentation files. The Skill only documents confirmed, non-trivial resolutions that pass all required-field and enum checks, maintaining documentation quality.

Related Skills