Skill Creator

A meta-skill that helps you create new skills for AI agent projects. This skill guides you through gathering requirements, generating properly structured SKILL.md files, and integrating with existing project patterns.

When to Use This Skill

Activate this skill when the user wants to:

Create a new skill

Make a skill

Generate a skill

Add a new skill to their project

Build a custom skill

Instructions

Follow these steps to help the user create a new skill:

Step 1: Gather Skill Information

Use the AskUserQuestion tool to collect the following information from the user:

1. **Skill Name**

- Ask: "What should we name this skill?"

- Explain that the name should be lowercase with hyphens (e.g., "project-creator", "responsive-nav", "api-generator")

- Store the response for use in file naming

2. **Skill Purpose**

- Ask: "What will this skill do?"

- Get a clear, detailed description of what the skill accomplishes

- Examples: "Create a new React component with TypeScript and tests", "Generate API endpoint with validation", "Add a responsive navigation component"

3. **Trigger Phrases**

- Ask: "What phrases should trigger this skill?"

- Request 3-5 natural trigger phrases that should activate the skill

- Examples: "create project card", "add new component", "generate API route"

4. **Optional: Additional Context**

- Ask if there are any specific patterns, file structures, or code templates to include

- Ask about integration with existing project conventions (design system, framework, style guide)

Step 2: Generate the Skill Directory and File

Once you have all the information:

1. Create the skill directory: `.claude/skills/{skill-name}/`

2. Create the main skill file: `.claude/skills/{skill-name}/SKILL.md`

Use the Bash tool to create the directory:

```bash

mkdir -p .claude/skills/{skill-name}

```

Step 3: Build the SKILL.md Content

Generate a SKILL.md file using this structure:

```markdown

{Skill Name Title Case}

{Brief description of what this skill does - 1-2 sentences}

Trigger Phrases

This skill activates when the user wants to {action description}:

"{trigger phrase 1}"

"{trigger phrase 2}"

"{trigger phrase 3}"

"{trigger phrase 4}"

"{trigger phrase 5}"

Instructions

When this skill is invoked, follow these steps:

Step 1: {First Major Step Name}

{Detailed instructions for this step. Be specific and actionable.}

1. {Substep 1 with clear action}

2. {Substep 2 with clear action}

3. {Substep 3 with clear action}

Step 2: {Second Major Step Name}

{Detailed instructions for this step.}

Step 3: {Third Major Step Name}

{Detailed instructions for this step.}

File Structure

{If this skill creates files, specify the structure:}

```

{directory}/

├── {file1}

├── {file2}

└── {file3}

```

Code Templates

{If applicable, include code templates or patterns:}

```{language}

// Example code with clear comments

```

Best Practices

{Best practice 1 specific to this skill}

{Best practice 2 specific to this skill}

{Best practice 3 specific to this skill}

Notes

{Important note 1}

{Important note 2}

```

Step 4: Customize the Template

Based on the user's responses:

1. **Replace all placeholders** with actual skill information

2. **Add specific, actionable instructions** relevant to the skill's purpose

3. **Include code templates** if the skill involves generating code (with proper syntax highlighting)

4. **Document file structure** if the skill creates multiple files

5. **Add domain-specific best practices** (e.g., accessibility, performance, security)

6. **Reference project conventions** if the skill integrates with an existing codebase

Step 5: Create the Skill File

1. Use the Write tool to create `.claude/skills/{skill-name}/SKILL.md` with the generated content

2. Verify the file was created successfully

3. Display a summary of what was created

Step 6: Provide Usage Instructions

After creating the skill, tell the user:

1. **How to activate it**: List the trigger phrases

2. **Where it's located**: Show the file path

3. **How to customize it**: Explain how to edit the SKILL.md file if needed

4. **How to test it**: Suggest using one of the trigger phrases to verify it works

Example Interaction

**User**: "Create a new skill"

**Assistant**:

1. ✅ Asks: "What should we name this skill?"

2. ✅ Asks: "What will this skill do?"

3. ✅ Asks: "What phrases should trigger this skill?"

4. ✅ Creates directory: `.claude/skills/example-skill/`

5. ✅ Generates `SKILL.md` with complete structure

6. ✅ Confirms creation and shows usage instructions

Tips for Creating Effective Skills

Scope and Focus

**Be specific**: Each skill should have a clear, focused purpose

**Single responsibility**: One skill = one well-defined task

**Composable**: Skills can reference or build upon other skills

Trigger Phrases

**Natural language**: Use phrases users would naturally say

**Multiple variations**: Include 3-5 different ways to express the same intent

**Action-oriented**: Start with verbs (create, add, generate, build, fix)

Instructions

**Step-by-step**: Break complex tasks into manageable steps

**Actionable**: Each step should have clear, executable instructions

**Context-aware**: Include checks for prerequisites and existing files

**Error handling**: Mention what to do if steps fail

Code Templates

**Complete examples**: Provide full, working code snippets

**Clear comments**: Explain what each section does

**Parameterized**: Use placeholders that are easy to replace

**Best practices**: Include proper error handling, types, validation

Integration

**Project conventions**: Reference design systems, style guides, and patterns

**Consistency**: Follow existing project structure and naming

**Dependencies**: Document required tools, libraries, or configurations

Project-Specific Patterns

When creating skills for different types of projects, consider these patterns:

Portfolio/Marketing Sites

Reference design system colors, spacing, typography

Ensure dark mode compatibility

Follow accessibility best practices (ARIA labels, semantic HTML)

Include responsive design patterns

Full-Stack Applications

Reference database schema and ORM patterns

Include API endpoint structure and validation

Follow authentication/authorization patterns

Consider environment-specific configurations

Component Libraries

Follow component naming conventions

Include prop types/interfaces

Provide usage examples

Document accessibility requirements

Developer Tools

Include CLI command patterns

Provide configuration file templates

Document required environment variables

Include testing patterns

File Location

Skills are stored in `.claude/skills/{skill-name}/SKILL.md`

Important Notes

Each skill should be self-contained and focused on one task

Skills can reference other skills if needed (e.g., "First, use the 'setup-env' skill...")

Keep instructions clear and actionable - avoid vague language

Test the skill after creation by using one of its trigger phrases

Update skills as project patterns evolve

Version control your skills directory for team sharing

Skill Creator

Skill Creator

When to Use This Skill

Instructions

Step 1: Gather Skill Information

Step 2: Generate the Skill Directory and File

Step 3: Build the SKILL.md Content

{Skill Name Title Case}

Trigger Phrases

Instructions

Step 1: {First Major Step Name}

Step 2: {Second Major Step Name}

Step 3: {Third Major Step Name}

File Structure

Code Templates

Best Practices

Notes

Step 4: Customize the Template

Step 5: Create the Skill File

Step 6: Provide Usage Instructions

Example Interaction

Tips for Creating Effective Skills

Scope and Focus

Trigger Phrases

Instructions

Code Templates

Integration

Project-Specific Patterns

Portfolio/Marketing Sites

Full-Stack Applications

Component Libraries

Developer Tools

File Location

Important Notes

Reviews (0)