unsupported-frontmatter

Name: unsupported-frontmatter
Availability: InStock
Author: xiongxianfei

Detect unsupported YAML frontmatter fields in SKILL.md files.

3|Updated Apr 19, 2026

Search Tags:#linting #discovery #yaml #metadata #validate #frontmatter #skill-discovery

Ready to run

npx skills add https://github.com/xiongxianfei/rigorloop --skill unsupported-frontmatter

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: unsupported-frontmatter
Source: https://github.com/xiongxianfei/rigorloop/tree/main/tests/fixtures/adapters/unsupported-frontmatter
Command: npx skills add https://github.com/xiongxianfei/rigorloop --skill unsupported-frontmatter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify skill definitions that include metadata fields not supported by the ecosystem, preventing invalid discoveries and potential adapter conflicts.

Core Features & Use Cases

Detects presence of unsupported YAML keys in SKILL.md frontmatter.
Emits a clear exclusion reason and guidance to fix metadata.
Integrates with local validation workflows to block publishing of invalid skills.

Quick Start

Run the validator against the skill directory to check for unsupported frontmatter.

Frequently Asked Questions about unsupported-frontmatter

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

FAQPage Schema

How do I validate YAML frontmatter in skill definitions for unsupported keys?▼

To validate YAML frontmatter, you can run a validator against the skill directory to detect unsupported metadata fields. This process checks the SKILL.md file to ensure only supported keys are present, returning a structured exclusion reason if extraneous fields are found.

What happens when skill discovery finds extraneous frontmatter fields?▼

When skill discovery finds extraneous frontmatter fields, the validator rejects the invalid skill and prevents it from propagating. It emits a clear exclusion reason and provides guidance to fix the metadata before publishing.

Do I need specific dependencies to check for unsupported metadata in SKILL.md files?▼

No specific dependencies are required to check for unsupported metadata in SKILL.md files. The validator operates as a standalone tool to inspect YAML frontmatter and identify any keys not supported by the ecosystem.

Why does my skill definition get rejected during adapter integration?▼

Your skill definition is rejected during adapter integration because it contains unsupported frontmatter fields. The validator requires YAML frontmatter with only a name and description, rejecting extraneous keys to prevent adapter conflicts.

Can I use local validation workflows to block publishing of invalid skills?▼

Yes, you can integrate this validator with local validation workflows to block the publishing of invalid skills. It detects unsupported YAML keys in SKILL.md frontmatter and emits guidance to fix metadata before release.