create-skill

Scaffold skill directories with SKILL.md templates and required frontmatter.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/Verbalist/agentic-workshop-1 --skill create-skill-verbalist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-skill
Source: https://github.com/Verbalist/agentic-workshop-1/tree/main/skills/utility/create-skill
Command: npx skills add https://github.com/Verbalist/agentic-workshop-1 --skill create-skill-verbalist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating a new skill often involves manual setup, inconsistent structure, and scattered documentation. This section explains how to scaffold a uniform, ready-to-publish skill.

Core Features & Use Cases

  • Standardized skeleton: automatically creates the recommended directory layout (skills/{category}/{skill_name}/) and a SKILL.md template.
  • Frontmatter enforcement: ensures required fields (name, description, version) are present for discoverability.
  • Catalog integration: demonstrates updating the skill catalog after scaffold.
  • Use Case: A developer wants to add a new utility skill quickly with proper docs and structure.

Quick Start

Create directory skills/{category}/{skill_name}/ and populate SKILL.md according to the template, then run the catalog-update script to refresh the marketplace.

Frequently Asked Questions about create-skill

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

FAQPage Schema
How do I scaffold a new skill with the correct directory layout and structure?

To scaffold a new skill, create the recommended directory structure at skills/{category}/{skill_name}/ and populate a SKILL.md file using a standardized template to ensure consistent layout and documentation.

What frontmatter fields are required for skill creation in the agentic-workflow marketplace?

Skill creation requires specific frontmatter fields in the SKILL.md file: name, description, and version. These enforced fields ensure proper discoverability and catalog integration for the new skill.

What is the best way to automate skill setup and ensure catalog integration?

The best way to automate skill setup is to use a scaffolding template that generates the skeleton, enforces required frontmatter, and includes a catalog-update script step to refresh the marketplace.

Do I need to manually update the skill catalog after creating a new skill skeleton?

You need to update the skill catalog after creating the skeleton. The workflow guides you to run a catalog-update script that refreshes the marketplace and integrates the newly scaffolded skill.

Why does my new skill template fail validation during the scaffolding workflow?

Skill template validation fails when required frontmatter fields are missing. The scaffolding workflow enforces the presence of name, description, and version fields, along with optional components, before proceeding.