Team skills
A team skill is a reusable workflow your AI coworkers can run, like drafting release notes or triaging a failed sync. A team rule is a convention every AI coworker follows; a skill is a procedure someone asks for. Write it once in your Team Context and it reaches your coworkers' coding agents. Skills written in plain prose also reach coworkers who never open a repository, in AI chat and in your Claude organization.
Add a skill
Each skill is a folder under agents/skills/ in Team Context (skills in the legacy coworkers/skills/ folder still load), with a SKILL.md at its root and any files it needs beside it. Publish one from a coding agent with ox skills publish, or commit the folder yourself. Team Context is a git repo, so every skill keeps its history.
Check where a skill runs
SageOx reads each skill and works out where it can run safely. Your team's Settings → Skills page shows the answer for every skill, who wrote it, and, when a skill can't run somewhere, why.
| A skill that… | Coding agents | Chat | Claude organization |
|---|---|---|---|
| Is written in plain prose | ✓ | ✓ | ✓ |
| Runs shell or ox commands, or declares the tools it may use | ✓ | — | — |
| Is scoped to specific repositories | ✓ | — | — |
| Bundles a script | ✓, once the script is approved in each repo | — | — |
- Coding agents. The ox CLI delivers team skills to coding agents in repos connected to your team, including Claude Code, Codex, Cursor, Gemini CLI, Amp, Droid, Goose, OpenCode, and Pi. See supported coding agents.
- AI chat. With SageOx connected over MCP, up to 12 team skills appear as prompts in tools that support them. Pick one from the SageOx connector and it becomes your own message, credited to the coworker who wrote it. Chat tools such as claude.ai and Claude Desktop list only skills written in plain prose.
- AI coworkers. Your AI coworker can find a skill through SageOx search and load it into the conversation. Skills that bundle a script or are scoped to a repository are never served over MCP.
- ox query.
ox queryreturns a matching team skill next to the discussions about the same problem. - Your Claude organization. See below.
Sync skills into your Claude organization
On a Claude Team or Enterprise plan, a team owner or admin can sync the team's plain-prose skills into your Claude organization. Claude then uses them in chat, Cowork, and Claude Code whenever someone asks.
- In Settings → Skills, under Claude organization, click Set up. SageOx shows what Claude's sync will copy before any token exists.
- Create the access token and copy it. SageOx shows it once.
- In Claude, open Organization settings → Git providers and add the token. Then open Plugins & skills → Add → Sync from GitLab, paste the repository URL, turn on Sync automatically, and set the plugin to Installed by default.
The card shows Connected once Claude's sync has pulled your skills.
Claude's sync copies your team's whole Team Context repository each time it runs: discussions, transcripts, docs, and skills, not only the skills. Owners of your Claude organization can reach that copy through Claude's Git settings; members see only the skills.
- Only skills written in plain prose reach Claude. Skills that run commands, bundle a script, or are scoped to a repository stay with coding agents.
- The export follows your team. SageOx refreshes it at least hourly, and Claude picks up skills added to or removed from Team Context on its next sync.
- The token only reads. It can't push to Team Context, and it expires after a year. Revoke it from the same card: Claude's next sync is refused and the export is removed.
Read and remove skills
Every coworker on the team can open a skill to read it rendered or as source, open its files, and see who wrote it. A skill's contents are shown as text; nothing inside a skill runs on the page.
Skills are written in Team Context, not on the Skills page. A team owner or admin can delete a skill from its page, which removes its folder from Team Context for every coworker in one commit.
If the skill changed since you opened it, SageOx stops the delete so you can review the new version first. Git history keeps the deleted version, so a revert brings it back.
In SageOx, only your team's members can list, read, load, or search its skills, on the web or through the SageOx connector. If you turn on Claude organization sync, members of your Claude organization also see the skills written in plain prose.
What's next
- Team rules: conventions every AI coworker follows, from the same Team Context
- Team Context: everything else that lives alongside your skills
- MCP overview: connect SageOx to Claude, ChatGPT, and other AI tools
- Supported coding agents: the coding tools the ox CLI works with
Team rules: share AI coding rules across repos and tools
Write team-wide AI coding conventions once in Team Context. Every AI coworker follows them in every repo: Claude Code, Cursor, Codex, and more.
Plans
The plan of record for work your team executes: mockups, GTM, rollouts, engineering. A visual page your coworkers act on, authored by your AI coworker, reviewed by you.