Use Skill Template

Create a new Claude Code skill following established patterns.

Note: Commands have been deprecated in favor of skills. This skill creates properly formatted SKILL.md files.

Execution Steps

1. Determine Skill Type

• Parse skill purpose from arguments
• Identify appropriate category (testing/development/analysis/quality)
• Choose suitable skill name (kebab-case format)

2. Apply Template

Create SKILL.md with required structure:

---
name: skill-name
description: 'This skill should be used when the user asks to "specific trigger 1", "specific trigger 2", "specific trigger 3". Brief description of what the skill does.'
version: "1.0.0"
last_updated: "YYYY-MM-DD"
user-invocable: true  # if user can invoke directly
argument-hint: "<argument_description>"  # if accepts arguments
---

# Skill Title

Brief overview of the skill's purpose.

## When to Use

- Trigger condition 1
- Trigger condition 2
- Trigger condition 3

## Process/Instructions

### Step 1: First Action
{Details}

### Step 2: Second Action
{Details}

## Output Format

{Expected output structure}

## Related Skills

- **related-skill-1**: Description
- **related-skill-2**: Description

3. Skill Directory Structure

Create skill in appropriate location:

plugins/{plugin-name}/skills/{category}/{skill-name}/
└── SKILL.md

4. Update Plugin Manifest

Add skill path to plugin.json:

{
  "skills": [
    "./skills/{category}/{skill-name}"
  ]
}

Best Practices

Naming:

• Use kebab-case for directory and skill names
• Use clear verb-noun format when applicable
• Keep names concise but descriptive

Description:

• Use third person: "This skill should be used when..."
• Include specific trigger phrases users would say
• List 3-5 concrete examples of when to invoke

Content:

• Keep skills focused on single responsibility
• Include at least one example usage
• Define clear output format
• Reference related skills

Example Usage

/use-command-template analyze API endpoints for rate limiting
/use-command-template validate database migrations for safety
/use-command-template generate Pydantic classes from schema

Migration Note

If migrating from old command format: