Command Development

Catalog Skill Units by validating SKILL.md frontmatter and returning structured YAML metadata.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/srobinson/nancy --skill command-development-srobinson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Command Development
Source: https://github.com/srobinson/nancy/tree/main/.agents/skills/Command%20Development
Command: npx skills add https://github.com/srobinson/nancy --skill command-development-srobinson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify and formalize every Skill Unit by ensuring a root SKILL.md with a YAML frontmatter that defines a name and description, enabling automatic discovery, versioning, and reuse across projects.

Core Features & Use Cases

  • Enforces a single entry point per Skill Unit via SKILL.md frontmatter.
  • Detects and documents optional directories (scripts/, references/, assets/) for on-demand usage.
  • Produces structured metadata for discovery, tooling, and marketplaces, including dependencies and components.

Quick Start

Instantiate a Skill Unit by placing SKILL.md at the root of the directory and adding optional resources as needed.

Frequently Asked Questions about Command Development

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

FAQPage Schema
How do I create reusable slash commands using markdown?

You create reusable slash commands by placing a SKILL.md file at your directory root and adding YAML frontmatter. This formalizes the Skill Unit for automatic discovery, versioning, and reuse across projects.

What is a SKILL.md file used for in command development?

A SKILL.md file serves as the single entry point for a Skill Unit, using YAML frontmatter to define the name and description. This enables automatic discovery, versioning, and reuse across projects.

How do I catalog valid Skill Units and validate frontmatter?

You catalog valid Skill Units by locating a root SKILL.md file and validating its YAML frontmatter. This evaluates optional components and resources, infers dependencies, and returns structured metadata for tooling.

What optional directories can I include when building plugin patterns?

When building plugin patterns, you can include optional scripts/, references/, and assets/ directories alongside your root SKILL.md. These are detected and documented for on-demand resource usage.

Do I need dependencies to generate structured YAML metadata for workflows?

No dependencies are required to generate structured YAML metadata for workflows. The Skill evaluates your SKILL.md and optional directories to infer dependencies and assets without external packages.