Docs/Build a skill
Use reference files
Keep the core workflow short while making deeper context easy to find.
Separate workflow from background#
The entry file should explain the task and how to complete it. Longer policies, detailed examples, and domain notes can live in references. Explain when the agent should consult each file.
Link to a specific resource#
Use a relative path and a useful label. Make the link part of the step where that information is needed.
## Draft the announcement
Use [the editorial guide](references/editorial-guide.md)
for tone and terminology. Start from
[the release template](assets/release-template.md).Keep references maintainable#
Organize long documents with headings. Check that links resolve after moving the folder. Put version or environment assumptions next to the guidance they affect.
Reference loading depends on the agent. Do not assume every supporting file is read automatically; important instructions must clearly point to the resources needed.
Read the primary reference: Agent Skills specification ↗