create-skill

Create reusable workflow skills with SKILL.md templates, validation, and packaging scripts.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/FahadImdad/Nexus-Fahad --skill create-skill-fahadimdad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-skill
Source: https://github.com/FahadImdad/Nexus-Fahad/tree/main/00-system/skills/skill-dev/create-skill
Command: npx skills add https://github.com/FahadImdad/Nexus-Fahad --skill create-skill-fahadimdad

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Turning a repeated workflow into a reusable AI skill requires knowing the SKILL.md format, frontmatter rules, naming conventions, and packaging steps, which is error-prone when done manually. ## Core Features & Use Cases - Guided Skill Creation Workflow: Walks through understanding use cases, planning resources, initializing structure, writing SKILL.md, and packaging into a distributable .skill file. - Scaffolding and Validation Scripts: init_skill.py generates a template skill directory, while quick_validate.py and package_skill.py validate frontmatter, naming, and structure before packaging. - Design Reference Library: Includes guides for descriptions, naming, output patterns, workflows, error recovery, and splitting large skills. - Use Case: After repeatedly running the same weekly report workflow, say "create skill" to capture it once as a packaged, validated skill that triggers automatically in future sessions. ## Quick Start Ask the AI to create a skill from the workflow you just completed, for example by saying "create a skill for generating my weekly status report".

Frequently Asked Questions about create-skill

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

FAQPage Schema
How do I create a reusable skill for Claude?

Run init_skill.py with a hyphen-case skill name to generate the directory template, then edit SKILL.md with a name, description, and workflow instructions. Finally run package_skill.py, which validates the structure and produces a distributable .skill file.

What is the required structure of a SKILL.md file?

SKILL.md requires YAML frontmatter containing only name and description fields, followed by a Markdown body with usage instructions. The body should stay under 500 lines, with detailed material moved into references files.

When should I add scripts, references, or assets to a skill?

Add scripts when the same code is rewritten repeatedly or deterministic execution is needed, references for documentation Claude should load on demand like schemas or API docs, and assets for files used in output such as templates or images.

Why does skill validation fail during packaging?

Common causes are extra YAML frontmatter fields beyond name and description, non-hyphen-case names, descriptions that are too short or generic, SKILL.md exceeding 500 lines, or references to files that do not exist.

How do I keep a large skill under the 500-line limit?

Split content by variant, domain, or feature into files under references/, keeping only the core workflow and navigation links in SKILL.md. Claude then loads only the relevant reference file for the current task.