Skill scraping
Pull skills from any registry, README or JSON feed into one catalog.
Guided or manual
Let AI draft the persona from a few answers, or write every field yourself.
Multi-target export
Claude Code, Codex, Cursor, Gemini CLI or raw MCP config.
EXPORT_TARGETS
one agent, five toolsRun one command and any MCP-capable model — Claude, GPT, Gemini — can call your agent's skills straight from the prompt.
npx -y @manudev.jsx/agents --agent ./agents-dev.agent.jsonWHO_IT_IS_FOR
three ways inOne repo, one persona
Compose once, drop CLAUDE.md in, and keep every picked skill in sync with one manifest.
Share by link
Send a share link — the recipient opens the exact same build and can fork it or export it to their own tool.
Ship agents as config
Export agent.json, serve it over MCP, and any model in your product can call the persona.
AGENT_JSON
one file, every tool{
"version": 2,
"name": "Untitled Agent",
"role": "general assistant",
"model": "claude-opus-5",
"temperature": 0.7,
"system": "You are a focused, pixel-precise engineering agent.",
"skills": [
{
"name": "QA",
"kind": "skills",
"repo": "mattpocock/skills"
}
],
"orchestrator": null,
"subagents": []
}HOW_IT_WORKS
compose → skills → install → serveFAQ
7 straight answersYes — the Free plan is $0: 3 saved agents, 10 AI drafts a month, the full skills.sh registry and every export target. Pro adds 25 agents, 200 drafts and MCP serving for $12.
To build one, yes — the composer saves agents and the drafts run on our model, so both need an account to attribute them to. Without one you get /demo: the whole flow, start to finish, on pre-loaded data.
The composer, the AI drafts and MCP tokens. Agents save to your account (GitHub OAuth, via Supabase) and follow you across devices — including anything you composed here before accounts existed.
A shared agent travels in the URL — no database row. The recipient opens the exact same build and saves their own copy.
Export gives you install commands per component. The skills CLI auto-detects Claude Code, Cursor and Codex and writes into their skills directory.
Yes — serve it over MCP. One command exposes the agent's persona and skills to any MCP-capable model.
Share links have a size cap. Export agent.json and drop it in the repo instead — same build, no limit.