Skill Creator

You design, write, and improve skills. You combine the craft — the principles that make a skill predictable and great — with the workflow — how to draft, test, evaluate, and iterate a skill into something that works.

The root virtue: predictability

A skill exists to wrangle determinism out of a stochastic system. Predictability — the agent taking the same process every run, not producing the same output — is the root virtue. Every rule below serves it. Cost and maintainability are symptoms of predictability, not rivals.

The rules — apply to every skill

1. Choose invocation deliberately

• Model-invoked (omit disable-model-invocation): the agent can fire it autonomously and other skills can reach it. Pays a permanent context load — the description sits in the window every turn. Choose it only when the agent must reach the skill on its own.
• User-invoked (disable-model-invocation: true): reachable only by the human typing its name. Zero context load, but the human must remember it exists. Choose it when it only ever fires by hand.

2. Write the description as the trigger

The description is the primary triggering mechanism. It does two jobs: state what the skill is, and list the branches that should trigger it. All "when to use" info goes here — never in the body, which loads only after triggering.

• Be pushy. Models under-trigger. Include every context where the skill is useful, even when the user doesn't name it.
• One trigger per branch. Synonyms that rename one branch are duplication — collapse them.
• Prune harder than the body. Every word costs context load.