Skill Creator
Overview
Guides users through creating well-structured Claude Agent Skills by gathering requirements, generating the skill structure, and producing properly formatted SKILL.md files.
Instructions
When helping create a new skill, follow this workflow:
Phase 1: Discovery
Ask the user about their skill requirements:
- •Purpose: "What should this skill help Claude do?"
- •Trigger: "When should Claude use this skill? What phrases or requests should activate it?"
- •Scope: "What are the boundaries? What should this skill NOT do?"
- •Examples: "Can you give me an example input and expected output?"
Phase 2: Design
Based on discovery, determine:
- •Skill name: lowercase, hyphens, max 64 chars
- •Category: creative, development, enterprise, or document
- •Description: clear trigger-focused description (max 1024 chars)
- •Structure: simple (SKILL.md only) or advanced (with scripts/templates)
Phase 3: Generation
Create the skill files:
- •Generate
SKILL.mdwith proper frontmatter - •Add clear instructions section
- •Include concrete examples
- •Add guidelines and constraints
- •Create supporting files if needed
Phase 4: Review
Present the generated skill and:
- •Explain each section's purpose
- •Suggest improvements
- •Offer to refine based on feedback
Output Format
SKILL.md Template
--- name: [skill-name] description: [Clear description explaining what this skill does and when Claude should use it] version: 1.0.0 --- # [Skill Name] ## Overview [Brief description of purpose] ## Instructions [Step-by-step guidance for Claude] ## Examples ### Example: [Use Case Name] **Input:** [Example user request] **Output:** [Expected response or action] ## Guidelines [Constraints and best practices]
Examples
Example: Create a Code Review Skill
User: "I want a skill that reviews Python code for best practices"
Response:
Let me help you create a Python code review skill. I have a few questions:
- •Should it focus on any specific aspects (security, performance, style)?
- •What coding standards should it follow (PEP 8, type hints)?
- •Should it suggest fixes or just identify issues?
[After gathering requirements, generate the skill]
Example: Create a Documentation Skill
User: "Create a skill for writing API documentation"
Response:
I'll help you build an API documentation skill. Let me understand your needs:
- •What format should the docs be in (Markdown, OpenAPI)?
- •Should it include code examples?
- •Any specific sections required (authentication, errors)?
Guidelines
- •Always start with discovery questions
- •Generate complete, working skills
- •Include realistic examples
- •Explain design decisions
- •Offer iteration opportunities
- •Follow marketplace standards
Checklist for Generated Skills
Before presenting a skill, verify:
- • Name follows conventions (lowercase, hyphens, ≤64 chars)
- • Description clearly explains trigger conditions
- • Instructions are step-by-step and clear
- • At least one concrete example included
- • Guidelines cover edge cases
- • No hardcoded secrets or credentials