creating-skills

Guides creation, validation, and packaging of Agent Skills with SKILL.md frontmatter.

9|2|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/AbdullahMalik17/Hacathan_5 --skill creating-skills-abdullahmalik17
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: creating-skills
Source: https://github.com/AbdullahMalik17/Hacathan_5/tree/main/.claude/skills/creating-skills
Command: npx skills add https://github.com/AbdullahMalik17/Hacathan_5 --skill creating-skills-abdullahmalik17

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Creating well-structured Agent Skills requires knowing the SKILL.md format, frontmatter rules, and resource organization, and mistakes lead to skills that fail validation or never trigger correctly. ## Core Features & Use Cases - Skill Scaffolding: Initialize a new skill directory with a SKILL.md template and example scripts, references, and assets using init_skill.py. - Validation and Packaging: Verify frontmatter, naming, and description rules with verify.py, then package the result into a distributable .skill file with package_skill.py. - Design Guidance: Apply progressive disclosure, description trigger rules, and workflow patterns from bundled references. - Use Case: When you want to build a new skill for a repeated workflow, use this Skill to scaffold the directory, write a compliant SKILL.md, validate it, and package it for distribution. ## Quick Start Create a new skill named pdf-merger in the current directory and validate its structure.

Frequently Asked Questions about creating-skills

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

FAQPage Schema
How do I create a new Agent Skill from scratch?▼

Run init_skill.py with a hyphen-case skill name and output path to generate the directory, a SKILL.md template, and example scripts, references, and assets folders. Then edit SKILL.md to complete the frontmatter and body instructions.

What should a SKILL.md description contain?▼

The description should state only triggering conditions, starting with "Use when" and optionally adding "NOT when" exclusions. It must never summarize the skill's workflow, since Claude may follow the description instead of reading the full skill body.

How do I validate a skill before packaging it?▼

Run verify.py against the skill folder to check YAML frontmatter, name format, the "Use when" trigger, and the presence of scripts/verify.py. If validation passes, package_skill.py creates a distributable .skill zip archive.

When should a skill include scripts versus references?▼

Use scripts for deterministic, repeatedly rewritten code that can execute without loading into context. Use references for documentation Claude should read on demand, keeping SKILL.md under 500 lines through progressive disclosure.

Why does my skill fail verification?▼

Common causes are missing YAML frontmatter, a name that is not lowercase hyphen-case, or a description lacking the "Use when" trigger. Run verify.py with the verbose flag to diagnose, fix the issue, and re-run validation.