SKILLS REGISTRY
Skills registry — manage, version, and share across AI tools
A skills registry is where your organisation publishes skills for the team to consume — with ownership, versions, and permissions. Joyst is that private registry: write once, manage across AI tools, and share without maintaining a fork per vendor — not a public skills marketplace.
FOR ORGS
What a skills registry is for organisations
- Org ownership
Someone owns a skill, drafts and publishes it, and the team consumes the approved version. Folders and permissions keep the catalogue tidy.
- Not a marketplace
A marketplace is public browse and download. Joyst is a private org registry — you manage your skills; you do not shop a public skill store.
- Publish → consume
The registry is where the organisation publishes skills for the team to consume — with ownership, versions, and permissions under one private catalogue.
ONE SOURCE OF TRUTH
Manage skills across AI tools
- Claude, Cursor, and agents as a manage job
One registry helps you manage skills across Claude, Cursor, agents, and other surfaces — so forks do not diverge unnoticed.
- One source of truth
Stop maintaining parallel skill trees per vendor. Write once in the private registry and sync from there.
- No forks per tool
Copying skills into each surface creates incompatible copies. Put the skill in the registry first so the team shares one owned build.
PORTABILITY
Skill portability across AI tools
- Sync and port
Port skills across the AI tools your team already uses. The registry stays the source of truth, not one vendor’s UI alone.
- MCP push and pull
Where MCP fits your setup, two-way push/pull keeps the catalogue and connected surfaces aligned.
- Manage across Claude and Cursor
If your team already uses Claude and Cursor skills, Joyst is for managing and syncing them across the team — not for browsing download listicles.
AGENTS PILLAR
Skills inside agents
- Package with MCPs and prompts
Skills rarely travel alone. Package them with MCPs and prompts into reusable agent setups so harnesses stay coherent.
- Beside the registry
The MCP catalogue and prompt management pillars sit beside the skills registry so packages use approved ingredients.
- Governed publishing
Who can publish and consume sits under AI governance — the same permissions model across the private team catalogue.
EXPLORE
Related pillars and guides
- Prompt management
Pair skills with versioned team prompts.
Open - MCP catalogue
Connect approved MCPs beside the registry.
Open - Agents
Package skills into reusable harness setups.
Open - AI governance
Permissions and audit on skills.
Open - Version and share skills
Draft, publish, ownership, and team sharing.
Open - Manage Claude & Cursor skills
One registry across the tools your team already uses.
Open - Skill portability
Sync and port skills without a fork per vendor.
Open
Skills registry FAQ
A controlled catalogue where your organisation writes, versions and shares skills for the team to consume — publish → consume, with clear ownership.
A marketplace is public browse and download. Joyst is a private org registry — you manage your skills; you don’t shop a public skill store.
Create your private skills registry
Create an organisation account and publish skills the team can consume — with ownership, versions, and permissions.
- Private org registry
- Draft → publish workflow
- Sync across AI tools