Skill Activation Patterns

A skill that fires at the wrong time is as useless as one that never fires. Design activation like you'd design a cron expression: specific, testable, boundaried.

When to Use

• Debugging skills that don't fire
• Two skills claiming the same trigger
• Skills firing on unrelated queries
• Designing a new suite with multiple related skills

The Activation Signal Stack

The model matches your skill against user queries using:

1. Name — weak signal
2. Description first sentence — strong signal, this is the "what"
3. "Use this skill when" line — strongest signal, the "when"
4. "Activate when" keyword list — pattern match against query phrases