Gareth MorgansProduct
Agent packages across harnesses -- assemble once, reuse cleanly
If every harness gets its own hand-built agent setup, you will rebuild the same ingredients under different names. Skills diverge. MCP connections go undocumented. Prompts drift. The “same” agent is not the same agent.
Packaging is the fix: define the ingredients once in a private AI agent library, then reuse that package across the harnesses your team already runs.
Related: how-to: create an agent package | ownership of skills and prompts | beside your IDP, not instead.
Rebuild pain
Teams typically:
Recreate prompts and skills inside each tool
Wire MCP servers ad hoc per laptop or project
Paste secrets into configs “just for this agent”
Lose track of which setup is approved
Onboarding means reverse-engineering someone's personal stack. Audits mean guessing.
What goes in a package
A Joyst agent package pulls from the private catalogue:
Skills from the skills registry
MCPs from the MCP catalogue
Prompts from prompt management
Secrets by reference from the secrets vault -- keys never enter model context as pasted text
Who can publish or use templates sits under AI governance.
Share and version -- not orchestrate
Packaging defines ingredients and setup. Orchestration runs multi-step or multi-agent workflows at runtime. Joyst focuses on packaging and catalogue -- not LangGraph-style orchestration platforms, and not a public agent marketplace.
Version the package when ingredients change. Share at private, group, or org level so the team gets one approved setup instead of five forks.
Share AI agents across harnesses
The catalogue holds one packaging of the setup. You use that packaging wherever the team works -- instead of maintaining a Cursor-only agent, a Claude-only agent, and a third “official” copy in a doc.
Parent product story: agents.
FAQ
What is an AI agent library?
A private catalogue of reusable, versioned agent setups for your organisation -- what each agent includes and who owns it.
Packaging vs orchestration?
Packaging = ingredients and ownership. Orchestration = runtime workflow engines. Joyst does the first job.
Is Joyst an agent marketplace?
No. Private org library only. No public “download agents” storefront.