Nufar Gaspar

And lastly, don't do like a monolithic blob, everything crammed into one file instead of using more of a folder structure.

So speaking of folder structure, the recommendation is to keep skill under 500 lines because it's a playbook, not the encyclopedia of everything that you do for work.

If you have reference materials or context that are very important for the skill, move them outside of the skill file into a separate set of files within the skill folder when it's relevant.

If you also have very long input and output examples, and you should include input and output examples, you can also put them in a separate examples.md files inside the skill repo or the skill folder that will help you a lot.

And that's probably the most effective way to communicate the desired format.

In terms of the discussion of whether or not I should append a bunch of files into my actual skill folder that will be bundled with the skill wherever the skill goes versus perhaps just pointing the skill to my other files and other systems, the deciding factor should be if this is something that is context specifically for this skill that should always come with the skill whenever I'm offloading the skill to someone else, then put it within the skill folder.

Otherwise, when it's stuff that are more general about you or about your company that can be pointed to an external source.

Let's show you a concrete skill that is slightly more advanced, and that is a meeting prep skill.

Obviously, all of us, no matter what we do, we have to get ready for meetings.

So I wanted to showcase an interesting skill here.

First of all, description, when to use, when users say prep for the meeting, meeting prep, and so on.

So it's offering quite a few options, so the skill will be picked up in almost all scenarios.

In terms of context required, so as part of the skill folder, I bundle stakeholder context.

So either it's going to be transient or if you have regular stakeholders that you work with, that can be fixed context file that comes with the skill.

It should get some email history for recency.

So that can, of course, be pulled directly from the user systems calendar and the other open action items involving the attendees.

In terms of the steps, identify all the attendees from the calendar or the other inputs, collect the context, analyze the agenda, run scenario analysis.

So part of what this skill does is kind of preparing you for what can go wrong with your meeting and generate a brief.

And the output will be a structure that is defined in an attached file because it's a very long and specific output.

And in broad strokes, the structure will be executive summary and so on.