skill-name

name	skill-name
description	Use when the user asks to [action] or says [trigger phrases]. Describe what the skill does and when to activate it. Include enough trigger phrases that the agent can recognize the context automatically.

Skill Title

One-line description of what this skill does and the engineering discipline it covers.

When to Activate

• Bullet list of specific scenarios
• That trigger this skill
• Be concrete, not vague

Core Principles

Principle Name

2-4 paragraphs of dense, non-obvious content. Each paragraph earns its place by teaching a technique or providing an actionable threshold. Avoid obvious statements.

Detailed Topics

Topic Name

Concrete guidance. Tables, code examples, and decision trees are preferred over prose paragraphs.

# Example code: conceptual, not framework-specific

Practical Guidance

Specific, actionable recommendations. Avoid "it depends" without also providing the decision criteria.

Gotchas

At least 5 experience-derived failure modes. This is the highest-signal section. Describe what goes wrong, why it goes wrong, and how to avoid it.

1. Gotcha name: description of the failure mode and how to avoid it.

Integration

Cross-references to related skills in this collection. Use plain skill names, not URLs.

• related-skill — one line explaining the relationship

References

• Reference Document — one line describing when to read it
• Script — one line describing what it does

Skill Metadata

Created: YYYY-MM-DD Version: 1.0.0