<skill-name-in-kebab-case>

Parse SKILL.md frontmatter to extract and validate Skill Unit metadata.

33|10|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/andreaswasita/copilot-cowork-dojo --skill skill-name-in-kebab-case-andreaswasita
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: <skill-name-in-kebab-case>
Source: https://github.com/andreaswasita/copilot-cowork-dojo/tree/main/template
Command: npx skills add https://github.com/andreaswasita/copilot-cowork-dojo --skill skill-name-in-kebab-case-andreaswasita

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This template skill provides a structural blueprint for turning raw repository content into discoverable Skill Units by enforcing a mandatory SKILL.md frontmatter and optional resource directories.

Core Features & Use Cases

  • Defines the required SKILL.md with name and description for discovery.
  • Supports optional directories such as scripts/, references/, and assets/ for extended capabilities.
  • Enables metadata extraction and validation during skill activation.

Quick Start

Place a SKILL.md at the root of a directory and ensure it contains a valid YAML frontmatter with name and description to register the Skill Unit.

Frequently Asked Questions about <skill-name-in-kebab-case>

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

FAQPage Schema
How do I automate skill discovery and metadata extraction from SKILL.md frontmatter?

You can automate skill discovery by placing a SKILL.md file with valid YAML frontmatter, specifically name and description, at your directory root. The system parses this metadata to validate, categorize, and index skills automatically.

What is the required frontmatter format for registering a Skill Unit?

The required frontmatter format for registering a Skill Unit is YAML syntax within a SKILL.md file. It must contain at least the name and description fields to pass validation and enable auto-discovery.

How do I structure directories with scripts and references for extended skill behavior?

To structure directories for extended skill behavior, place your SKILL.md at the root and add optional directories like scripts/, references/, and assets/. The discovery mechanism indexes these resources alongside the core metadata.

Does skill validation require any external dependencies or components?

Skill validation does not require external dependencies or components. It operates natively by parsing the SKILL.md frontmatter to ensure safe categorization, metadata extraction, and indexing without additional packages.

What happens if a SKILL.md file is missing the description field during indexing?

If a SKILL.md file is missing the description field, safe validation fails because both name and description are mandatory. The skill unit will not pass categorization checks or be registered for auto-discovery.