Skip to main content
This is where an agent gets its behavior. Two parts: instructions (the how) and skills (the what).
The Skills library — every skillset available to your agents

​
Instructions

Instructions are plain-language direction for the agent. Write them the way you’d brief a capable preparer. For example:
“You are an R&D tax specialist. For each client, review payroll and project documentation, identify qualifying activities, and draft the credit calculation with citations.”
Good instructions are specific about the output you want (a cited draft, a summary memo, a particular format) and any standards to follow.

​
Skills

Skills are the capabilities the agent may use. Turn on only what the work needs. Tags indicate origin — DEFAULT skills are broadly available; ORG skills are specific to your organization. Open a skill to see its instruction and the files packaged with it.
A skill's detail page — its SKILL.md instruction alongside the templates, references, and scripts bundled with it

​
The key distinction: capability is not access

Enabling a skill lets the agent use that capability — it does not widen what data the agent can see. “Read documents” lets the agent read the documents it has been granted access to, nothing more. Data access is controlled separately (see Setting Doc Store access and Access scoping).
Holding these two ideas apart is the most important thing on this page: skills = what it can do; access = what it can see.

​
Quick vs Advanced

On the Quick path, the task template picks the instructions and skills for a standard process — you can tweak the instruction text but don’t manage the skill list. On Advanced, you write instructions and select skills yourself.

​
Next steps

  1. Agents, Spaces, and Skills
  2. Setting Doc Store access
  3. Skills vs plugins