Use and create skills
A skill is a reusable instruction manual: a method, template, reference collection, or workflow an assistant can follow for a particular kind of task.
On this page
Skill or agent
The agent does the work; the skill explains a method. One assistant might use both an onboarding checklist and an interview-summary skill. Several assistants can reuse the same method.
A skill does not automatically grant permissions or install every tool it mentions. Its dependencies must actually be available.
Start in the marketplace
Open the skills tab in the marketplace. Read a skill's purpose, scope, and requirements before installing it into an agent you can manage.
Test it with a small example and check the result. Public availability does not mean every official skill is automatically installed on every agent.
Reference or clone
| Option | Meaning | Choose it when |
|---|---|---|
| Reference | Use the source-maintained version | You want source updates |
| Clone | Keep an independent copy | You need your own editable procedure |
Swipe sideways to see more of a wide table.
A reference is generally read-only at its source and may stop working if the source is removed or revoked. A clone does not automatically receive future source changes.
Make a skill without coding
First complete a task successfully in conversation. Then ask for a draft of the method:
Turn the monthly report workflow we just tested into a skill draft. Include when to use it, required inputs, steps, an output template, and error handling. Mark missing amounts for confirmation instead of filling them in. Show me the draft before publishing anything.
Create or maintain it through organization skill management. Its entry file is called SKILL.md; think of it as the manual's first page.
What to include
Describe suitable tasks, required files and tools, ordered steps, output format and location, handling of missing or conflicting data, and actions requiring confirmation.
Include real templates and examples. “Be careful” or “ensure quality” is less useful than a specific check the assistant can perform.
Maintain and publish
Retest after edits. If concurrent changes cause a conflict, read the latest version and merge intentionally instead of overwriting colleagues' work.
Keep internal processes private when appropriate. Before publishing, remove customer data, internal addresses, account details, and secrets, and confirm that you may share the included materials.