example-file-validation

Validate example files against live hyoka schemas to detect drift.

3|5|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/ronniegeraghty/hyoka --skill example-file-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: example-file-validation
Source: https://github.com/ronniegeraghty/hyoka/tree/main/.squad/skills/example-file-validation
Command: npx skills add https://github.com/ronniegeraghty/hyoka --skill example-file-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drift can accumulate in non-primary paths like examples, seed templates, and docs, causing mismatches between in-repo artifacts and the live schemas used by hyoka.

Core Features & Use Cases

  • Schema drift detection: compares prompts, configs, and criteria example files against the official schemas to surface deviations.
  • Path coverage awareness: highlights areas not covered by the standard hyoka validate workflow (e.g., examples/, .hyoka seeds, docs snippets).
  • Guided remediation: provides actionable recommendations to align example files with the current validation rules.

Quick Start

Run hyoka validate to compare example files against your active schemas and generate a drift report.

Frequently Asked Questions about example-file-validation

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

FAQPage Schema
How do I validate example files against schemas to detect drift?

To validate example files against schemas, this Skill reads YAML frontmatter in prompts, configs, and criteria samples, then compares them to live schemas to identify drift and report discrepancies with remediation guidance.

What is schema drift in non-standard repository paths?

Schema drift in non-standard paths occurs when in-repo artifacts like examples, seed templates, and docs snippets become misaligned with the live validation rules, causing mismatches that are not caught by primary validation commands.

How do I check example files in paths not covered by the standard validate command?

To check example files in uncovered paths, the Skill specifically targets areas missed by standard workflows, scanning examples directories, seed templates, and docs snippets to compare their structure against active schemas.

Does this validation tool work with YAML frontmatter in prompts and configs?

Yes, this validation tool works with YAML frontmatter by reading the metadata defined in prompts, configs, and criteria sample files, directly comparing the extracted frontmatter against the defined schemas to surface deviations.

What is the best way to fix discrepancies between seed templates and schemas?

The best way to fix discrepancies is to use the guided remediation provided by the validation report, which offers actionable recommendations to align your seed templates and example files with the current schema rules.