CreateSkill

Create and validate skill directories with standardized SKILL.md frontmatter.

7|3|Updated Jan 15, 2026

Search Tags:#yaml #skill #generate #validate #workflows #frontmatter #skill-system

Ready to run

npx skills add https://github.com/Zpankz/mcp-skillset --skill createskill-zpankz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: CreateSkill
Source: https://github.com/Zpankz/mcp-skillset/tree/main/CreateSkill
Command: npx skills add https://github.com/Zpankz/mcp-skillset --skill createskill-zpankz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It standardizes the process of creating and validating new skills by ensuring each Skill unit follows the required structure, frontmatter, and references.

Core Features & Use Cases

Enforces a consistent SKILL.md frontmatter with mandatory fields (name and description).
Guides canonicalization and validation of skill directories, naming, and referenced workflows.
Supports a repeatable process for creating new skills or canonicalizing existing ones, with a clear validation path.

Quick Start

Follow the CreateSkill workflow to initialize a new skill directory, add SKILL.md with required frontmatter, and run the pack validator to verify references.

Frequently Asked Questions about CreateSkill

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

FAQPage Schema

How do I standardize skill creation and validate frontmatter structure at scale?▼

Standardize skill creation by enforcing consistent SKILL.md frontmatter with mandatory fields, TitleCase naming conventions, and required workflow references. Validation ensures each skill unit adheres to the required directory structure and pack references before deployment.

What is the required SKILL.md frontmatter format for generating a new skill?▼

The required SKILL.md frontmatter must include mandatory name and description fields. This frontmatter validates the presence of SKILL.md and referenced workflows, while supporting optional assets like scripts and references to maintain structural consistency.

How do I validate referenced workflows and directory naming when creating skills?▼

Validate referenced workflows and directory naming by running the pack validator after initializing the skill directory. This verifies that all workflow references exist, TitleCase naming is applied, and the skill structure adheres to canonicalization rules.

Can I canonicalize existing skills without regenerating their entire directory structure?▼

Canonicalize existing skills by validating their current SKILL.md frontmatter, enforcing TitleCase naming, and checking referenced workflows. This repeatable process ensures compliance without fully regenerating directories, supported by optional assets like scripts and references.

What limitations exist when validating optional assets like scripts and references in a skill?▼

Validation focuses primarily on mandatory SKILL.md frontmatter, required sections, and workflow references. Optional assets such as scripts, references, and assets are supported but are not the core validation target, meaning missing optional components may not trigger validation failures.

Does the skill creation workflow require dependencies or external components to validate?▼

The skill creation workflow requires no external dependencies or components to validate. It operates standalone to enforce SKILL.md frontmatter, TitleCase naming, and workflow references, ensuring new skills adhere to required structural standards independently.