create-skill

Creates modular agent skills with SKILL.md YAML frontmatter and concise bodies.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/tkmh04/CoffeeHouse-Management-System --skill create-skill-tkmh04
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-skill
Source: https://github.com/tkmh04/CoffeeHouse-Management-System/tree/main/.agents/skills/create-skill
Command: npx skills add https://github.com/tkmh04/CoffeeHouse-Management-System --skill create-skill-tkmh04

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Guides teams to create modular, self-contained skills that extend agent capabilities by providing structured guidance, reusable patterns, and clear frontmatter conventions.

Core Features & Use Cases

  • Enforces YAML frontmatter with name and description to enable discovery.
  • Keeps skill body concise (ideally under 200 lines) to optimize activation.
  • Encourages progressive disclosure via references/assets/scripts to house longer guidance.
  • Supports a standard skill structure for deterministic execution and on-demand resources.

Quick Start

Define SKILL.md with YAML frontmatter including name and description, keep the body concise, and add optional references if needed to split longer content.

Frequently Asked Questions about create-skill

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

FAQPage Schema
How do I create an AI agent skill with YAML frontmatter?

To create an AI agent skill, define a SKILL.md file with YAML frontmatter containing the name and description fields, keep the body concise, and add optional references or scripts for bundled resources.

What is progressive disclosure for modular skill authoring?

Progressive disclosure in modular skill authoring splits longer guidance into bundled references, assets, and scripts, keeping the main SKILL.md body concise and under 200 lines to optimize activation.

What's the best way to structure documentation for deterministic AI tasks?

The best way to structure documentation for deterministic AI tasks is using a self-contained skill format with YAML frontmatter, a concise SKILL.md body, and optional scripts or references for on-demand resources.

Does my SKILL.md file need to stay under a certain line count?

Yes, your SKILL.md file should ideally stay under 200 lines to optimize agent activation, moving longer content into bundled references, assets, or scripts to maintain a concise body.

Can I include external scripts and references when building agent skills?

Yes, you can include optional scripts, references, and assets when building agent skills, housing longer guidance in these bundled resources instead of bloating the main SKILL.md body.

Why does my AI agent skill fail to activate properly?

Agent skill activation may fail if the SKILL.md lacks required YAML frontmatter fields like name and description, or if the body exceeds 200 lines, which prevents optimal discovery and execution.