Joyst

VERSION AND SHARE SKILLS

Version and share skills. Clear ownership for the team.

If skills live as Slack files or private copies, nobody has a shared library. Joyst gives you skill version control and team sharing inside a private skills library: drafts and published versions, folders, permissions and updates your agents can use.

dash.joyst.app
Versioning and sharing skills in Joyst

FOR TEAMS

Ownership that scales when you version and share skills

  • Team skills library (private)

    A team skills library is where your organisation keeps skills with owners. It is not a public pack browser. Private by default. Shared on purpose.

  • Share skills with clear ownership

    When you version and share skills, someone owns each one. Updates go to the published library instead of hidden copies in Slack and local folders.

  • Not a marketplace

    This is your private skills library, with folders, permissions, drafts and published versions. Not public skill packs.

SKILL VERSION CONTROL

Draft vs published. Skill version control.

  • Draft while you iterate

    Draft skills stay out of the way. Publish when the team and its agents should use them.

  • Published as the shared version

    Skill version control makes the published version the one everyone uses. History shows what the team should run, and lets you go back when needed.

  • Central updates agents check for

    When a skill improves, agents should run the published version, not last month’s copy. Central updates make sure they do.

  • Works with managing across tools

    If you also manage skills across AI tools, versioning and sharing make the central registry trustworthy.

ACCESS

Folders and permissions

  • Folders group related skills

    Folders organise the private library, so teams can find and own related skills instead of keeping everything in one long list.

  • Permissions for view, use and manage

    Permissions decide who can view, use or manage. Platform or AI operations teams can publish. Wider groups can use.

  • Governed publishing

    Link publishing rights to AI governance when security needs to know who can change what goes into agents. Package skills into agents with MCP servers and prompts.

  • Share deliberately

    Share skills through folders and permissions, not by pasting files into chat. Ownership stays clear as the library grows.

RELATED

Keep exploring.

  • Manage skills across AI tools

    One registry across Claude, Cursor and agents.

    Open
  • Skill portability

    Sync and move skills without a copy for each vendor.

    Open
  • Manage Claude & Cursor skills

    Manage Claude skills and Cursor rules in one registry.

    Open
  • Agents

    Package skills, prompts, MCP servers and secrets into reusable setups.

    Open
  • MCP catalogue

    Connect, document and approve MCP servers.

    Open
  • AI governance

    Permissions and an audit trail across the private catalogue.

    Open
  • Prompt management

    A team prompt library with versioning and sharing levels.

    Open

Version and share skills FAQ

Skills have draft and published versions with a history, so you know what the team should run and can go back when needed.

People with manage rights on the skill or folder. View and use rights can be wider than publishing rights.

Agents can check for updates to published skills, so they are not stuck on old copies. Managing skills across AI tools adds porting and sync.

No. It is a private skills library for your organisation, not a marketplace.

No. Joyst is the private team catalogue for skills, prompts, MCP servers, secrets and agents.

Share skills with your team

Create an organisation account and bring skills, prompts, MCP servers, secrets and agents into one private catalogue.

  • Private to your organisation
  • Draft, then publish
  • Limited open beta
Start free beta