test-skill

Validates SKILL.md presence and frontmatter structure for Skill Units.

3|Updated Aug 18, 2025
One-click install
npx skills add https://github.com/rileyseaburg/codetether --skill test-skill-rileyseaburg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-skill
Source: https://github.com/rileyseaburg/codetether/tree/main/opencode/.opencode/skill/test-skill
Command: npx skills add https://github.com/rileyseaburg/codetether --skill test-skill-rileyseaburg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This test skill validates the Skill Unit discovery and metadata generation workflow by ensuring SKILL.md is present and properly formatted, and that the unit's metadata can be generated from its frontmatter.

Core Features & Use Cases

  • Validates presence and structure of SKILL.md at the Skill root.
  • Extracts name and description from YAML frontmatter to populate discovery fields.
  • Serves as a safety test to confirm downstream tooling can parse and index Skill Units.

Quick Start

Invoke the Skill validation flow on this unit to verify frontmatter integrity and metadata extraction.

Frequently Asked Questions about test-skill

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

FAQPage Schema
How do I validate YAML frontmatter and SKILL.md structure for a skill unit?

Validating YAML frontmatter and SKILL.md structure requires verifying the presence of required fields at the Skill root to ensure metadata can be correctly extracted and parsed for downstream tooling.

What is the best way to check if skill unit metadata is correctly formatted for discovery?

Checking skill unit metadata formatting involves extracting the name and description from YAML frontmatter, ensuring required fields are present, and confirming dependencies and components are correctly identified.

How does frontmatter validation work when no scripts or references are present in a skill unit?

Frontmatter validation works by detecting the SKILL.md file and verifying its structure regardless of scripts or references, ensuring the unit's metadata can be generated solely from its frontmatter fields.

Can I use skill unit validation for repository analysis and metadata generation tasks?

Yes, skill unit validation applies to repository analysis and metadata generation tasks by confirming frontmatter integrity, verifying dependencies, and ensuring safety checks are correctly identified for downstream indexing.

Why does downstream tooling fail to parse and index skill units with missing frontmatter fields?

Downstream tooling fails to parse skill units with missing frontmatter fields because required metadata cannot be extracted, preventing proper validation of dependencies, components, and safety checks needed for indexing.

Do I need a SKILL.md file at the skill root to validate metadata workflows?

Yes, a SKILL.md file at the skill root is required for validating metadata workflows, as it contains the YAML frontmatter from which name, description, and other required fields are extracted and verified.