report-schema

Parse, validate, and normalize YAML Autoreport contracts across loader, model, and validator components.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/tubtrb/autoreport --skill report-schema
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: report-schema
Source: https://github.com/tubtrb/autoreport/tree/main/codex/skills/report-schema
Command: npx skills add https://github.com/tubtrb/autoreport --skill report-schema

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill ensures reliable loading, validation, and alignment of YAML-based contract data across the Autoreport workflow, enabling consistent schema enforcement for templates, payloads, and tests.

Core Features & Use Cases

  • YAML parsing, schema validation, and normalization for loader.py, models.py, and validator.py.
  • Public examples, preload references, and tests to keep contracts and payload shapes in sync with the template-driven flow.
  • Use cases include validating contract drafts, example payloads, and runtime payload consistency across deck generation.

Quick Start

Prompt an AI to verify and align the Autoreport schema by loading example files and validating a draft against the public contract spec.

Frequently Asked Questions about report-schema

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

FAQPage Schema
How do I validate YAML contract payloads before generating reports?

To validate YAML contract payloads, parse and normalize the data against a schema to enforce deterministic behavior. This surfaces contract errors in a stable, test-driven order, ensuring consistent runtime payload consistency across deck generation.

Why does my YAML schema validation fail with inconsistent errors?

YAML schema validation produces inconsistent errors when normalization paths are not enforced. Applying validation rules across loader and validator components guarantees deterministic behavior and surfaces contract errors in a stable, test-driven order.

What is the best way to enforce schema rules for YAML template contracts?

The best way to enforce schema rules for YAML template contracts is to apply validation and normalization across loader and model components. This guarantees deterministic behavior and aligns payload shapes with the template-driven flow.

Can I use contract validation to check example payloads during deck generation?

Yes, contract validation can check example payloads during deck generation. Validating contract drafts and example files against the public contract spec keeps payloads in sync and ensures runtime payload consistency throughout the workflow.

Does YAML contract validation require a specific loader for normalizing data?

YAML contract validation requires a loader that parses and normalizes data to guarantee deterministic behavior. The loader works with model and validator components to apply schema rules and surface contract errors consistently.