Quick Answer
All six support skills, and most let an admin share them across a team. Version history and usage reporting are thin almost everywhere. No vendor delivers your skills live into a competitor's AI: Microsoft's business skills reach Claude desktop and Claude Code, and Cursor shares the open SKILL.md format, but neither keeps skills in sync across vendors. Teams that use more than one AI end up keeping a copy of each skill in each tool.
The Matrix
Checked November 13, 2026 against each vendor's documentation.
| AI tool | Custom skills | Shared across a team | Version history | Usage reporting | Reaches other AIs |
|---|---|---|---|---|---|
| Claude | Yes, in the open SKILL.md format | Owners can give a skill to everyone on Team and Enterprise | Version pinning in the API only; no rollback in the admin view | Smart reports suggest work to package as skills (beta) | No. Custom skills don't sync even between Claude's own apps |
| ChatGPT | Yes, as skills inside plugins | Admins can publish skills to the workspace | Not documented for skills | Use counts over the last 30 days | No |
| Microsoft Copilot | Business skills (public preview), and SKILL.md files in Cowork | Admins roll skills and agents out centrally | In preview for business skills | Agent analytics | Business skills reach Claude desktop and Claude Code through Microsoft's Dataverse MCP server |
| Gemini | Workspace skills, announced September 2026, replacing Gems | Admin curation coming; Gemini Enterprise shares by email | Owner-only history in Gemini Enterprise | Not documented | No. Skills made in the Gemini app aren't available in Workspace or Gemini Enterprise |
| Grok | Yes, with a Skill Creator, since May 2026 | Shared across the Bots in a Grok Bot workspace | Not documented | Not documented | No |
| Cursor | Yes, in the open SKILL.md format, since January 2026 | Through your repository, or a team marketplace on Teams and Enterprise | Through Git | Not documented | Same open format, but nothing keeps copies in sync |
What the Matrix Shows
- Skills are standard now. Every tool supports them, and most use or accept the open SKILL.md format, so a well-written skill is portable.
- Sharing works inside one vendor. Claude, ChatGPT and Copilot all let an admin give a skill to the whole team, as long as the team uses that one tool.
- Control is thin. Rolling back a bad change is rare, and only ChatGPT and Copilot report how skills are used.
- Nothing crosses vendors live. A skill updated in Claude stays old in ChatGPT until someone copies it across. Even Claude's own apps don't share custom skills.
If Your Team Uses More Than One AI
Most teams do. Some people prefer Claude for writing, others use ChatGPT, the business runs on Microsoft 365, and developers work in Cursor. Each tool's own skills only reach the people using that tool, so the same skill gets copied into each one and the copies drift apart.
The fix is to keep each skill in one place and deliver it to every AI from there, with one version history and one view of what gets used.
Where Contexta Fits
Contexta holds your company's skills and context in one place and delivers them to Claude, ChatGPT, Copilot, Cursor and Grok through one connection. Update a skill once and every connected AI uses the new version on its next request. Every change is versioned and can be restored, and one view shows which skills are used in which AI. Your knowledge base stays in your own SharePoint or Google Drive. See Integrations for setup.