Gareth MorgansProduct
Agent packages across harnesses. Assemble once, reuse cleanly.
When every AI tool gets its own hand-built agent setup, teams rebuild the same parts under different names. Skills diverge, MCP connections go undocumented and prompts drift. Before long, the “same” agent is several different agents.
The answer is packaging. Define the parts once in a private AI agent library, then reuse that package in every tool your team already uses.
Related: how-to: create an agent package | ownership of skills and prompts | beside your IDP, not instead.
Rebuild pain
Without packaging, teams typically:
Recreate prompts and skills inside each tool
Connect MCP servers one laptop or project at a time
Paste secrets into configs “just for this agent”
Lose track of which setup is approved
New starters have to reverse-engineer a colleague’s personal setup, and audits come down to guesswork.
What goes in a package
A Joyst agent package draws on the private catalogue:
Skills from the skills registry
MCPs from the MCP catalogue
Prompts from prompt management
Secrets by reference from the secrets vault, designed to keep keys out of the model’s context
Who can publish or use templates is set in AI governance.
Share and version. Not orchestrate.
Packaging defines what an agent includes and how it is set up. Orchestration runs multi-step or multi-agent workflows as they happen. Joyst handles packaging and the catalogue. It is not an orchestration platform like LangGraph, and it is not a public agent marketplace.
Version the package when its parts change. Share it privately, with a group or with the whole organisation, so the team works from one approved setup instead of five copies.
Share AI agents across harnesses
The catalogue holds one package for each setup. The team uses that package wherever it works, instead of maintaining a Cursor agent, a Claude agent and a third “official” copy in a document.
Read more about agents.
FAQ
What is an AI agent library?
It is a private catalogue of reusable, versioned agent setups for your organisation. It records what each agent includes and who owns it.
How is packaging different from orchestration?
Packaging covers what an agent includes and who owns it. Orchestration is the engine that runs workflows as they happen. Joyst does the first job.
Is Joyst an agent marketplace?
No. Joyst is a private library for your organisation. There is no public storefront for downloading agents.