Nufar Gaspar

The most important part is the beginning, and that is the trigger.

The trigger is how you instruct the tool on when to discover and when to basically fire this skill.

And it's probably the most important line, because if your trigger is not very precise or very meek,

then your skill will just not be used and selected by the agent.

So I would advise actually that you make it louder rather than quieter because the models will sometimes skip past more subdued descriptions.

So trigger words, exact descriptions about when do you expect to be used, and be more explicit than implicit here.

That will go a long way.

And then we have the body and what most people go wrong with the body that they write prose and skills are like playbooks.

So favored and numbered steps or bulleted lists.

Claude and all of the AI tools, they really like structured instructions dramatically because that will also turn to be their action plan if it's very, very concrete.

So try to make it as literal as possible.

That's how the tools like to follow the instructions.

However, I want you to also set the right level of freedom.

So if a task is very fragile, like a database migration, coding, acquiring something that has to be very precise, be very prescriptive with a step-by-step.

But if it's more of a creative task, like writing a strategy doc or something that is more open to interpretation, give the guidance, but do leave some room for the tool to be creative because if you're over-railroading the model, you will not get as good results.

We also encourage you to make sure to include an output format.

And here, it's even better if you just include an output example.

So show the model, don't just describe.

If you want a template, include it.

If the output is a table, show a table and headers.