skills-create

Creates and refactors Claude Code skills using progressive disclosure standards.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/az9713/claude-code-hooks-tutorial --skill skills-create-az9713
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skills-create
Source: https://github.com/az9713/claude-code-hooks-tutorial/tree/main/skills/.claude/skills/skills-create
Command: npx skills add https://github.com/az9713/claude-code-hooks-tutorial --skill skills-create-az9713

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing a well-structured Claude Code skill requires knowing frontmatter rules, trigger-rich descriptions, progressive disclosure, and validation gates. This Skill encodes that craft so new skills are authored correctly and bloated existing skills get split into lean SKILL.md files plus on-demand references. ## Core Features & Use Cases - Create mode: Scaffolds a new skill from a template, gathers trigger phrases and context, plans references/templates/scripts, and validates the result. - Refactor mode: Splits a fat SKILL.md by extracting bulky detail into references/ and templates/ while preserving behavior with mandatory-read pointers. - Standards enforcement: Applies shared craft rules covering skill types, frontmatter spec, writing voice, no-duplication, and a seven-gate validation checklist. - Use Case: You have a 400-line SKILL.md that costs tokens on every run. Invoke refactor mode to extract the output template and edge-case catalog into references/, leaving a lean spine that behaves identically. ## Quick Start Ask the agent to create a new skill named pdf-report using the skills-create workflow, providing the trigger phrases and task description when prompted.

Frequently Asked Questions about skills-create

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

FAQPage Schema
How do I create a new Claude Code skill?▼

Gather the trigger phrases and task context first, then scaffold SKILL.md from the provided template into .claude/skills/<name>/. Write a third-person trigger-rich description and a lean imperative body, pushing detail into references/, then run the validation gates.

How to refactor a long SKILL.md file?▼

Inventory each block as spine or extractable, move bulky content verbatim into references/ or templates/, and replace it with pointers. Always-needed output formats need a mandatory-read line so the agent does not skip them, and behavior preservation must be verified.

What should a skill description contain to trigger reliably?▼

A description must be third person, state what the skill does and when to use it, and include literal trigger phrases users would say plus the /name invocation. Vague descriptions like 'helps with documents' fail to auto-invoke.

When should I not build a skill?▼

Skip building a skill for one-off tasks or when a tool's owner already ships a good one. A rough threshold is the Rule of Three: if you have prompted the same process about three times, bank it as a skill.

What is the biggest risk when splitting a skill into references?▼

Moving an always-needed output format into a lazily-loaded reference, so the agent forgets to read it and the output silently changes. Always pair such an extraction with a mandatory-read line and verify it in the behavior-preservation gate.