Why use skills
- You explain the procedure once. You do not paste the same instructions into every new chat.
- Every agent does it the same way. The agent in your editor and the one in your chat app follow the same steps.
- A fix reaches everyone. Improve the procedure and each agent reads the new version the next time it uses the skill.
- A new teammate’s agent is ready on day one. Joining the team puts the team’s skills in reach.
Example. A sales team saves a skill called “call-notes”: what to pull from a call recording, how to word the follow-up, where to file it. Whichever agent a rep uses, the follow-up comes out the same way. When the team adds “always confirm the next meeting date”, every agent picks it up on its next call.
Save a procedure
A skill is a small folder. Its main file holds the instructions, a name and a one-line description of when to use it. It can carry supporting files such as a checklist or a template. You do not build the folder by hand. Tell your agent how the work is done and ask it to save that as a skill. A new skill starts private to its owner.Example. A consulting partner walks her agent through how she reviews a deal memo before the partner meeting. She says, “Save this as a skill called deal-review.” The checklist she pasted becomes a supporting file.
Decide who it belongs to
A skill is either yours or a team’s.
Access is checked every time. Someone who leaves a team stops seeing its skills the next time their agent asks.
Example. An agency keeps “client-report” as a team skill, so every account manager’s agent builds reports the same way. One manager keeps “my-inbox-rules” as her own.
Let agents find and follow it
An agent sees the skills in its reach, each with its description, and reads one when the work in front of it matches. The description is how the agent decides, so write it as “Use when…”. Each time an agent uses a skill it gets the latest version. There is nothing to reinstall after a change.Example. A support lead asks, “Process this refund request.” Her agent sees the team skill “refunds”, described as “Use when a customer asks for money back”, reads it and follows its steps.
Improve it over time
Each change is saved as a new version, and the earlier versions stay listed. If two people change the same skill at once, the second change is refused, not saved over the first. That person’s agent fetches the current version, merges the two and publishes again.Share a skill by link
You can share a skill with anyone by link. The link opens a page that shows the instructions and the files, and how to use the skill with an agent. Anyone who has the link can read it without signing in. The page is not listed or searchable anywhere.Example. A dev team shares its “release-checklist” skill with a contractor by link. The contractor’s agent follows it without joining the team. When the contract ends, the team stops sharing.
Skill or pinned file?
If the instructions only make sense inside one workspace, pin them there. If an agent needs them to start the work at all, save a skill. A pinned file is found only after someone tells the agent which workspace to open. A skill is in reach of every agent you or your team connect.What you see
- Skills (in your avatar’s menu): the skills you and your teams host.
- A skill’s page: the instructions, Versions, who it is Available to, and How to load it with an agent.
- Share by link and Stop sharing: turn the public page on and off.
- Delete skill: removes the skill and every version. It cannot be undone.
- The shared page: what someone with the link sees, with Use with an agent.
Ask your agent
- “Save how we just did this as a skill called weekly-report.”
- “What skills do you have?”
- “Use the deal-review skill on this memo.”
- “Update the call-notes skill: always confirm the next meeting date.”
- “Share the release-checklist skill by link and give me the link.”
Good to know
- A skill’s name is lowercase letters, digits and hyphens, up to 64 characters. You use a name once among your own skills, and a team uses it once among its own.
- One version holds up to 512 files and 16 MB in total.
- A private skill has no public page, even for you. You see it on the Skills page.
- When you stop sharing, the link stops working on the next read. Copies someone already installed on their own machine stay there.
- Joining a team puts its skills in reach of every agent you connect. That is why you join a team yourself, in your own browser.
- An agent you connected as read only can read skills but cannot publish one.
For agents and developers
Skill rules
The folder format, reach, publishing, versions and sharing
MCP server
How a connected agent lists and reads skills