Skill Creator

Produce a skill that changes how an agent handles a recurring task. Keep only instructions, resources, and constraints that contribute to that outcome.

Establish the gap

Use the request, existing skill, and applicable repository instructions to identify the missing behavior and what completion requires. Inspect only resources relevant to the change. Ask for missing information only when it changes the scope, contract, or authorization.

• Reuse an existing skill when its scope already fits; fix its routing if discovery is the problem.
• Create a skill only for a distinct recurring capability. Keep one-off inputs in the task prompt and repository-wide conventions in repository instructions.
• Preserve supported behavior, metadata, user decisions, and authorization boundaries unless their change is part of the request.
• Separate the observed failure from a proposed remedy. Try deleting or narrowing conflicting instructions before adding another rule.

Author the smallest useful instruction set

Brief, clear, specific, useful. Assume competence in ordinary domain knowledge and tool use. Retain non-obvious constraints, decision criteria, output contracts, and verification that prevent a concrete failure. Ground technical claims in the current implementation, a real run, or a primary source; qualify uncertain conditions.

Define the outcome and when work is complete. Prescribe a sequence only when order matters; otherwise let the agent choose the method. Record genuine approval boundaries without inserting review stops into already-authorized work. Do not turn a workaround for one model into a universal requirement.