Name a Skill and describe when to use it
Describe a Skill’s task and activation conditions, then distinguish metadata parsing from host selection checks.
Describe a Skill’s task and activation conditions, then distinguish metadata parsing from host selection checks.
Define invocation arguments and map accepted flags to behavior.
Describe both activation cases and exclusions for a skill.
Compose existing capabilities through named inputs and outputs.
Improve a skill against preserved tasks, baselines and observable assertions.
Assemble single-purpose prompt fragments under explicit inclusion conditions.
Test skill rules under realistic pressure against a no-skill baseline.
Retire a distributed capability with replacement and migration information.
Separate portable capability instructions from host-specific tool bindings.
Choose automatic or user invocation according to discovery needs and human control.
Evaluate instruction text according to whether it defines a tool contract, routes a task or directs loaded behavior.
Choose broad guidance, parameterized recipes or exact commands according to the task’s justified variation and failure cost.
Avoid maintaining a stale prose cache of cheap executable environment facts.
Promote only recurring actionable principles with a stated failure consequence and a comparison against existing rules.
Make keep, improve, retire and merge verdicts state the evidence, action and replacement rather than a vague label.
Promote a local learned behavior only after checking recurrence, scope and counter-evidence.
Preserve operational controls in agent instructions when translating or adapting prose.
Keep example-language syntax separate from the host's invocation-template syntax.
Separate translated explanation from literal symbols used by an instruction loader or reference resolver.
Turn an accepted successful interaction trace into a deterministic reusable procedure, then verify replay against its accepted evidence.