unknown-field

Validate SKILL.md frontmatter for mandatory name and description fields.

23.2k|2.2k|Updated Dec 31, 2025
One-click install
npx skills add https://github.com/can1357/oh-my-pi --skill unknown-field
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unknown-field
Source: https://github.com/can1357/oh-my-pi/tree/main/packages/coding-agent/test/fixtures/skills/unknown-field
Command: npx skills add https://github.com/can1357/oh-my-pi --skill unknown-field

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill validates Skill Units by ensuring the mandatory frontmatter fields exist, enabling reliable discovery even when SKILL.md contains extra or unknown keys.

Core Features & Use Cases

  • Validation of mandatory fields (name, description) at the Skill Unit root.
  • Graceful handling of additional, non-standard frontmatter fields without breaking discovery.
  • Use Case: When a Skill Unit SKILL.md includes extra metadata, the system still recognizes and loads the core information.

Quick Start

Provide the Skill Unit's SKILL.md and run the discovery check to ensure the required fields exist and unknown fields are ignored.

Frequently Asked Questions about unknown-field

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

FAQPage Schema
How do I validate YAML frontmatter in a SKILL.md file with extra fields?

YAML frontmatter validation for SKILL.md files checks mandatory fields (name and description) while gracefully ignoring extra non-standard keys. This ensures accurate skill discovery without breaking when unexpected metadata is present at the root.

What happens during skill discovery if my frontmatter contains unknown keys?

During skill discovery, unknown frontmatter keys are ignored without causing parsing errors. The system reads the root YAML, validates the required name and description fields exist, and safely bypasses any additional non-critical metadata.

How do I parse root YAML frontmatter and report empty dependencies?

Parsing root YAML frontmatter extracts mandatory fields and reports dependencies as an empty array when no scripts are present. This satisfies parsing requirements by focusing on critical keys and ignoring non-essential metadata.

Do I need a strict YAML schema to validate mandatory frontmatter fields?

A strict YAML schema is not required to validate mandatory frontmatter fields. The validation specifically enforces the presence of name and description at the root, allowing other unknown fields to pass through without triggering errors.

Can I use custom metadata in SKILL.md frontmatter without breaking discovery?

Custom metadata in SKILL.md frontmatter does not break discovery. The validation process applies graceful handling for additional non-standard fields, ensuring the system still recognizes and loads core information accurately.

What are the limitations of ignoring unknown fields in frontmatter validation?

Ignoring unknown fields in frontmatter validation means non-critical keys are bypassed entirely. If those extra fields contained necessary operational data, they would not be parsed during discovery, as the system only enforces mandatory name and description fields.