Create a skill
Add a directory containingSKILL.md under the agent:
Use the skill
Skills do not need a hook. OpenComputer packages the entireskills/ directory
with that agent, which can load a matching skill during the session.
Tell the agent when the skill should guide its work:
Add supporting files
Keep the core procedure inSKILL.md. Put longer material beside it:
SKILL.md so the agent knows when to read them.
Supporting files are deployed with the skill and need no imports from
agent.ts. Loading a skill lists them, and the agent reads one on request —
so a long checklist or a set of examples costs nothing until it is needed.
An agent can only read files packaged with the skill it loaded. There is no
path out of that directory, and no way to reach anything else on the machine.
Scope skills to an agent
Skills live underopencomputer/agents/<agent-id>/skills/, so each deployment
receives only its own skill set. To reuse a skill, copy or generate the skill
directory into each agent that needs it.
Skills versus tools
Many useful workflows combine both: a research skill explains the process
while the GTM engineer example uses an Exa
search tool to retrieve current sources.