3.3 Good vs. Bad Descriptions
Good vs. Bad Descriptions
Your description makes or breaks skill activation
Good Descriptions: Specific and Actionable
Figma Design Analyzer
Analyzes Figma design files and generates documentation for developer handoff. Use when user uploads .fig files, asks for 'design specs', 'component documentation' or 'design-to-code handoff'.
Linear Project Manager
Manages Linear project workflows including sprint planning, task creation, and status tracking. Use when user mentions 'sprint', 'Linear tasks', 'project planning' or asks to 'create tickets'.
Bad Descriptions: Avoid These
Too Vague
Helps with projects.
Too Technical
Implements the Project entity model with hierarchical relationships.
The Description Formula
What It Does
Clear statement of the core action: 'Generates weekly sales reports from CSV data'
When to Use It
Trigger context: 'Use when user asks for report, summary, or status update'
Key Capabilities
What makes it special: 'Includes charts, comparisons, and trend analysis'
Formula Template
[What it does] + [When to use it] + [Key capabilities] = Great description
Description Quality Test
Read your description out loud. If a stranger could understand when to use this Skill, your description is good enough. If not, add more context and trigger phrases.
Reálné příklady popisů, které fungují — a těch, které ne.
There are no comments for now.