Gareth MorgansProduct
Manage skills across Claude and Cursor, without maintaining forks
If you keep one skill definition in Claude and another in Cursor, you do not have a portable skill. You have two forks. The next edit lands in one place and not the other. New starters inherit whichever copy someone remembered.
Claude and Cursor are good places to use skills. They are a poor place to keep the only copy of what your team knows.
Start free beta | Manage skills across AI tools
Related: skill portability | manage Claude and Cursor skills | how-to: add and sync a skill | AI governance | private MCP catalog vs marketplace.
Manage skills across tools. The fork problem.
Teams usually end up with:
A Claude skill (or project instruction) tuned for one workflow
A Cursor rule or skill file on a laptop that "mostly matches"
A copy pasted into Slack whenever someone asks for the latest version
An agent that still uses last month's wording
Each tool is built for personal speed. None of them is a catalogue for the organisation, with an owner, a publishing step and a way to update everyone who uses the skill.
Registry model instead of forks
A skills registry holds the skill once:
One owned definition with clear share levels
Draft and published states, so experiments stay out of everyday use
Version history whenever the skill changes. See version and share skills
Sync, so Claude, Cursor and other tools use the published copy instead of a local fork
You still work in Claude and Cursor. You stop treating each tool as a separate source of truth.
Sync and port without rewriting
Portability means moving and updating skills across AI tools without rewriting the same guidance for each one.
In Joyst, you publish centrally, then sync and update so everyone picks up the approved version. Read more on the product page: manage skills across AI tools.
Keep API keys out of skill text. Put credentials in the secrets vault.
What this is not
This is not a list of the best Claude skills to download, nor a public marketplace of strangers’ packs. It is about managing skills privately for your organisation. Claude and Cursor are where the skills are used, not what the product is.
FAQ
Do we have to leave Claude or Cursor?
No. Joyst is the registry and source of truth. Teams still run skills in the tools they already use.
Is this the same as Cursor rules in a repo?
Repository rules help one project. A registry covers ownership, share levels, versioning and reuse across several AI tools, not just one repository.
Can agents use the same skills?
Yes. Published skills feed agent packages so packaged setups stay aligned with the registry.