Skill Development
Create or update agent skills (SKILL.md plus optional scripts and references) so Claude-style agents gain repeatable workflows and domain procedures.
Overview
Skill Development is an agent skill most often used in Build (also Operate) that guides you through creating or updating effective SKILL.md packages with workflows, integrations, and bundled resources.
Install
npx skills add https://github.com/anthropics/claude-plugins-official --skill skill-developmentWhat is this skill?
- Explains skills as modular packages with required SKILL.md and optional bundled resources
- Covers specialized workflows, tool integrations, domain expertise, and bundled scripts
- Documents standard layout: scripts/, references/, and assets under a skill folder
- Positions skills as onboarding guides that turn general agents into specialists
- Intended when users want to create a new skill or update an existing one
- Required skill anatomy: SKILL.md with YAML name and description plus optional scripts, references, and assets directorie
Adoption & trust: 3.2k installs on skills.sh; 29.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want reusable agent capabilities but do not know how to structure SKILL.md metadata, triggers, and optional scripts so agents invoke them reliably.
Who is it for?
Solo builders formalizing repeated agent workflows into installable skills for Claude plugins or personal skill directories.
Skip if: One-off tasks with no repetition, or teams that only need MCP servers without procedural SKILL.md packaging.
When should I use this skill?
Users want to create a new skill or update an existing skill that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
What do I get? / Deliverables
You ship a well-formed skill folder with clear frontmatter, instructions, and optional resources that extend your agent like a specialized onboarding guide.
- SKILL.md with valid YAML frontmatter (name, description) and instruction body
- Optional bundled scripts, references, and assets folder layout
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Build → agent-tooling because packaging procedural knowledge into skills is how solo builders extend their coding agents during product construction. Agent-tooling is where skills, plugins, and capability bundles are authored—not where end-user features ship alone.
Where it fits
Scaffold a new deployment checklist skill with scripts/ for your monorepo.
Document API-specific steps and references for a third-party webhook skill.
Refactor an outdated SKILL.md description so agents trigger the skill on the right user phrases.
How it compares
Meta authoring guide for SKILL.md packages—not a domain task skill and not a substitute for runtime MCP tool servers.
Common Questions / FAQ
Who is skill-development for?
Indie developers and skill authors who extend Claude or compatible agents with modular, self-contained procedural packages.
When should I use skill-development?
During Build when adding agent-tooling; in Operate when iterating skills after production learnings; whenever you create or update a skill’s workflows and bundled resources.
Is skill-development safe to install?
Review the Security Audits panel on this Prism page and LICENSE.txt terms bundled with the official plugin skill before copying patterns into your repo.
SKILL.md
READMESKILL.md - Skill Development
# Skill Creator This skill provides guidance for creating effective skills. ## About Skills Skills are modular, self-contained packages that extend Claude's capabilities by providing specialized knowledge, workflows, and tools. Think of them as "onboarding guides" for specific domains or tasks—they transform Claude from a general-purpose agent into a specialized agent equipped with procedural knowledge that no model can fully possess. ### What Skills Provide 1. Specialized workflows - Multi-step procedures for specific domains 2. Tool integrations - Instructions for working with specific file formats or APIs 3. Domain expertise - Company-specific knowledge, schemas, business logic 4. Bundled resources - Scripts, references, and assets for complex and repetitive tasks ### Anatomy of a Skill Every skill consists of a required SKILL.md file and optional bundled resources: ``` skill-name/ ├── SKILL.md (required) │ ├── YAML frontmatter metadata (required) │ │ ├── name: (required) │ │ └── description: (required) │ └── Markdown instructions (required) └── Bundled Resources (optional) ├── scripts/ - Executable code (Python/Bash/etc.) ├── references/ - Documentation intended to be loaded into context as needed └── assets/ - Files used in output (templates, icons, fonts, etc.) ``` #### SKILL.md (required) **Metadata Quality:** The `name` and `description` in YAML frontmatter determine when Claude will use the skill. Be specific about what the skill does and when to use it. Use the third-person (e.g. "This skill should be used when..." instead of "Use this skill when..."). #### Bundled Resources (optional) ##### Scripts (`scripts/`) Executable code (Python/Bash/etc.) for tasks that require deterministic reliability or are repeatedly rewritten. - **When to include**: When the same code is being rewritten repeatedly or deterministic reliability is needed - **Example**: `scripts/rotate_pdf.py` for PDF rotation tasks - **Benefits**: Token efficient, deterministic, may be executed without loading into context - **Note**: Scripts may still need to be read by Claude for patching or environment-specific adjustments ##### References (`references/`) Documentation and reference material intended to be loaded as needed into context to inform Claude's process and thinking. - **When to include**: For documentation that Claude should reference while working - **Examples**: `references/finance.md` for financial schemas, `references/mnda.md` for company NDA template, `references/policies.md` for company policies, `references/api_docs.md` for API specifications - **Use cases**: Database schemas, API documentation, domain knowledge, company policies, detailed workflow guides - **Benefits**: Keeps SKILL.md lean, loaded only when Claude determines it's needed - **Best practice**: If files are large (>10k words), include grep search patterns in SKILL.md - **Avoid duplication**: Information should live in either SKILL.md or references files, not both. Prefer references files for detailed information unless it's truly core to the skill—this keeps SKILL.md lean while making information discoverable without hogging the context window. Keep only essential procedural instructions and workflow guidance in SKILL.md; move detailed reference material, schemas, and examples to references files. ##### Assets (`assets/`) Files not intended to be loaded into context, but rather used within the output Claude produces. - **When to include**: When the skill needs files that will be used in the final output - **Examples**: `assets/logo.png` for brand assets, `assets/slides.pptx` for PowerPoint templates, `a