Quick Start

YAML
---
name: example-skill-name
description: Third-person description with trigger phrases. Use when [specific scenario].
---

# Quick Start
[Immediate actionable example]

# Workflow
1. Step one
2. Step two
3. Step three

# Examples
**Example 1:**
Input: [specific input]
Output: [specific output]

# Best Practices
- Key guideline 1
- Key guideline 2

# Common Pitfalls
- What to avoid

Workflow

1. Analyze Requirements - Extract the core expertise and methodology
2. Create YAML Frontmatter - Follow naming and description rules
3. Structure Content - Organize into the five key sections
4. Add Concrete Examples - Include specific input/output pairs
5. Validate Format - Ensure proper YAML and markdown structure

Progress:

• Requirements analyzed
• YAML frontmatter created
• Quick start section written
• Workflow documented
• Examples added
• Best practices listed
• Common pitfalls identified
• Format validated

Examples

Example 1: Input: "Expert at analyzing financial statements and creating investment recommendations" Output:

YAML
---
name: analyzing-financial-statements
description: Analyzes financial statements and creates investment recommendations. Use when evaluating companies for investment decisions.
---

Example 2: Input: "Specialist in debugging Python code and optimizing performance" Output:

YAML
---
name: debugging-python-code
description: Debugs Python code and optimizes performance issues. Use when encountering errors, slow execution, or memory problems.
---

Best Practices

• Use gerund form for skill names (verb-ing)
• Keep descriptions under 1024 characters with clear triggers
• Start with immediate actionable content (no preamble)
• Include concrete examples with specific inputs/outputs
• Target ~500 lines maximum per skill
• Provide default approaches rather than multiple options

Common Pitfalls

• Using first or second person in descriptions ("I analyze" or "You can")
• Creating names that aren't gerund form or use invalid characters
• Starting with explanatory text instead of Quick Start
• Writing abstract descriptions without concrete examples
• Making skills too long or complex for a single file