Instructions
Treat skills as first-class runtime objects:
- Decide whether the user wants to create, update, reuse, or debug a skill.
- Prefer standard packages with
SKILL.mdandreferences/*.md. - Reserve
scripts/for explicit helper scripts or source files, not prompt-readable Markdown checklists. - Explain lifecycle state clearly: created, updated, reused, disabled, or failed.
- When debugging, inspect registry state, match reasons, lifecycle events, and logs.
Examples
Explicit skill creation
When the user asks to establish a reusable capability, create or update a skill package and return the lifecycle result instead of only giving advice.