skill-name

Validate SKILL.md frontmatter and directory structure for Skill Units.

2|Updated Apr 3, 2026

Search Tags:#automation #validation #scaffold #repository #skill #yaml-frontmatter #unit

Ready to run

npx skills add https://github.com/jscott3201/ai-agent-skills --skill skill-name-jscott3201

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: skill-name
Source: https://github.com/jscott3201/ai-agent-skills/tree/main/skills/_template
Command: npx skills add https://github.com/jscott3201/ai-agent-skills --skill skill-name-jscott3201

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This template provides a standardized scaffold for Skill Units, ensuring each unit has a SKILL.md with mandatory frontmatter and a detectable root structure. It also surfaces a metadata surface that downstream tooling can consume to automate skill discovery and onboarding.

Core Features & Use Cases

Validates the presence of SKILL.md and required fields (name and description).
Detects optional component directories (scripts, references, assets) and surfaces their availability for on-demand use.
Emits a metadata payload including name, tagline, description, request, complexity, category, keywords, dependencies, components, and toxicity flags for tooling and discovery.

Quick Start

Create a new skill directory under skills/ with a SKILL.md frontmatter containing name and description, and optionally add scripts/, references/, or assets/ as needed.

Frequently Asked Questions about skill-name

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

FAQPage Schema

How do I scaffold a new skill repository with the correct directory structure?▼

To scaffold a skill repository, create a new directory under skills/ containing a SKILL.md file with mandatory YAML frontmatter fields for name and description, then optionally add scripts, references, or assets directories for component integration.

What is the required frontmatter validation for a SKILL.md file?▼

SKILL.md frontmatter validation checks for the mandatory presence of name and description fields, then compiles optional metadata including tagline, request, complexity, category, keywords, dependencies, components, and toxicity flags into a structured payload.

How does skill automation detect optional components like scripts and references?▼

Skill automation detects optional components by checking the newly created skill directory for the presence of scripts/, references/, and assets/ subdirectories, surfacing their availability for on-demand integration during the onboarding process.

Can I use this template to generate a metadata payload for downstream tooling discovery?▼

Yes, you can use this template to generate a metadata payload. It compiles validated frontmatter and detected components into a structured object that downstream tooling consumes to automate skill discovery and onboarding.

What is the best way to ensure my new skill unit passes frontmatter checks?▼

The best way to pass frontmatter checks is to include both name and description fields in your SKILL.md YAML frontmatter and organize your skill directory under the skills/ path to trigger the automated validation process.

Why does my skill directory fail validation when adding new skill units?▼

Skill directory validation fails when the SKILL.md file is missing or lacks the mandatory name and description frontmatter fields required to enforce the standardized scaffold for skill units.