full-fixture

Validate all reserved frontmatter fields and nested references against the skill schema.

8|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/usurobor/cnos --skill full-fixture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: full-fixture
Source: https://github.com/usurobor/cnos/tree/main/schemas/fixtures/skill-frontmatter/valid/full
Command: npx skills add https://github.com/usurobor/cnos --skill full-fixture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a complete frontmatter-driven fixture to validate the skill schema by exercising every reserved field at least once, including nested references.

Core Features & Use Cases

  • Comprehensive frontmatter field coverage to test schema validation.
  • Includes a nested sub-skill reference via calls to sub/SKILL.md to verify relative path resolution.
  • Used by tools/validate-skill-frontmatter.sh to ensure compatibility with the frontmatter schema across real-world skills.

Quick Start

Run the schema validator against this fixture to confirm that all fields are accepted.

Frequently Asked Questions about full-fixture

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

FAQPage Schema
How do I validate a complete frontmatter schema with all reserved fields?

Use a full fixture to validate a frontmatter schema by exercising every reserved field at least once, ensuring fields like name, description, artifact_class, and parent are correctly defined along with nested sub-skill references.

What is frontmatter schema validation used for in markdown testing?

Frontmatter schema validation in markdown testing is used to verify that a frontmatter-driven unit exercises every reserved field and nested relationship correctly, ensuring complete compatibility with the official frontmatter schema across real-world skills.

Does the frontmatter validator test nested sub-skill references and relative paths?

Yes, frontmatter validation tests nested sub-skill references by including a call to a nested sub/SKILL.md path, verifying that relative path resolution works correctly within the complete frontmatter schema fixture.

How do I test dynamic references and nested calls in a frontmatter fixture?

You test dynamic references and nested calls in a frontmatter fixture by applying the fixture to a scenario where the unit exercises every reserved field, validating fields like calls, calls_dynamic, runs_after, and runs_before against the schema.

What reserved fields are required when validating a complete frontmatter fixture?

Required reserved fields when validating a frontmatter fixture include name, description, artifact_class, kata_surface, governing_question, visibility, triggers, scope, inputs, outputs, requires, calls, calls_dynamic, runs_after, runs_before, excludes, and parent.

When do I need a full frontmatter fixture instead of a basic schema validation?

You need a full frontmatter fixture instead of basic schema validation when the unit exercises every reserved field and nested relationship, such as dynamic references and sub-skill calls, requiring comprehensive compatibility testing across real-world skills.