Skills: using them

A skill is a reusable package of instructions and files that teaches an agent to do something specific and do it the same way every time — produce your house-style report, run your QA checklist, drive a system with a fiddly API.

Where a tool is a single capability, a skill is know-how: the procedure, the templates, and any scripts that go with it.

Who can do what

Task	User	Agent owner	Admin
Browse the skills gallery	✅	✅	✅
See skills available to the organization	✅	✅	✅
Attach a skill to an agent	— as Editor	✅	✅
Create a skill	✅	✅	✅
Control which skills the organization can use	—	—	✅
Decide which agents may author skills	—	—	✅

Finding skills

• Skills Gallery — public skills, browsable and searchable, with no sign-in needed.
• Agent → Settings → Skills — what's available to your organization, and what this agent has.

Each skill shows what it does, what it contains, and its status.

Attaching one

Attach from Agent → Settings → Skills. The skill's files are staged into the agent's sandbox under /skills/<name>/, where the agent can read them and run anything executable they contain. They also appear read-only in the agent's Skills file zone.

Detaching removes the skill from that agent. It doesn't delete the skill.

Using one

You don't invoke a skill explicitly. The agent knows which skills it has and what each is for, and reaches for the right one — ask for the thing, not for the skill.

If an agent isn't using a skill you expect, it's usually because the skill's description doesn't match how you phrased the request. That's a fixable authoring problem — see Skills: authoring & publishing.

Skills need the right tools

A skill that runs a script needs the agent to have the run tool; one that writes files needs the file tools. Attaching a skill doesn't grant tools. If a skill misbehaves, check the agent's tools before the skill itself.

Visibility

Every skill has a visibility scope:

Scope	Who can use it
Private	Only the organization that created it
Tenant	Every agent in that organization
Public	Discoverable by any organization

Admins set the organization's default and can change any skill's scope — see Skills governance.

Creating one

Anyone can create a skill; agents can too, if an admin has granted that agent skill-authoring permission. See Skills: authoring & publishing.