Create a custom skill for your team
Package a capability so every assistant and agent in your org can use it.
Advanced · ~15 min · Prerequisites: org admin or builder role
What you'll do
Decide when a custom skill is the right move, define what it does, publish it to your org, and confirm your teammates can invoke it from chat.
When to build one
A custom skill is worth building when you have a capability that multiple people (or agents) need to invoke the same way — a standardized prompt pattern, a domain-specific tool call, or a repeatable transformation that your org runs often.
Skip the build if an existing common or org skill already covers the job. Check Browsing skills first.
Good candidates:
- A prompt template your team reuses constantly (e.g. "format a design brief from bullet points")
- A tool call that wraps an internal API
- A multi-step pattern that always runs in the same order
Define the skill
Open the skills builder (your org admin can find this in the skills management area). Give the skill:
- Name — what appears after
/in the composer; keep it short and action-oriented - Description — one sentence explaining what it does; this is what the model reads when deciding whether to invoke it
- Prompt template — the instruction the assistant follows, including any
{{placeholders}}the user fills in - Scope — set to Org so every teammate and every agent in your org can see and use it
Keep the build mechanics light here — for full field-by-field reference, see Creating skills.
Share it
Save and publish the skill. It appears immediately in the Skills group of the / slash menu for everyone in your org — no per-user install needed. Agents scoped to your org also gain access automatically.
If you need to restrict it to a specific custom agent rather than the whole org, set scope to Agent and select the target agent. That skill won't appear in the general library.
Use it from chat
Open a new thread, type /, scroll to Skills, and pick your skill. The composer pre-fills /your-skill-name Help me with: …. Fill in the prompt and send — the assistant runs the skill the same way it would any other.
Ask a teammate to do the same in their session to confirm org-scope is working. If the skill doesn't show up for them, verify the scope is set to Org (not Agent or Common-draft) and that they have the appropriate role.
Editing a skill's prompt template takes effect immediately for all future invocations — existing scheduled tasks that reference the skill pick up the change on their next run.