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 fine as runtimes. They are a poor place to store the only copy of team capability.
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 Slack paste when someone asks for the latest version
An agent that still uses last month's wording
Each surface optimises for personal speed. None of them is an org catalogue with an owner, a publish gate, and a path to update every consumer.
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 off the live path
Version history when the skill changes -- see version and share skills
Sync so Claude, Cursor, and other surfaces consume 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 is the job: move and update skills across AI tools without rewriting the same guidance for every harness.
In Joyst that means central publish, then sync and update so consumers pick up the approved version. Detail 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 "best Claude skills" download list. It is not a public marketplace of strangers' packs. It is private org management -- Claude and Cursor as modifiers on a management problem, not as the product category.
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?
Repo rules help one project. A registry covers ownership, share tiers, versioning, and reuse across multiple AI surfaces -- not only one git tree.
Can agents use the same skills?
Yes. Published skills feed agent packages so packaged setups stay aligned with the registry.