Studio
From prompts to workflows, agents and bots
Chain the prompts you already use into workflows, package them as skills, and run them in your agent or as a bot. Everything exports to open formats, so nothing is locked in here.
Building blocks
- 01
Prompt
One instruction you paste into a chat. The library has thousands.
- 02
Skill
A SKILL.md folder an agent loads when a task matches. Steps, rules, scripts, references.
- 03
Workflow
Prompts, skills and tools in a fixed order, with branches, parallel steps and approvals.
- 04
Agents
A lead agent plans and hands parts to subagents, each with its own context and tools.
- 05
Bot
A workflow that starts on its own: a Slack message, a schedule, a new pull request.
Try it
Four ways in
Ready-to-use workflows
Templates for content, code review, research, support and ops. Fill in the inputs, run them with Claude, or take them to your own agent.
Workflow builder
Add steps, branch, run workers in parallel, add an approval, then run it with Claude and watch every step.
Skills
Ready-to-use SKILL.md files with one-command install, and a creator for your own.
My studio
Your saved workflows and skills, and the result of every run.
Patterns
Six shapes cover most workflows
Start with the simplest one that works. Add more agents only when steps are independent or need a clean context: multi-agent runs cost several times the tokens.
Prompt chain
Fixed steps, each feeding the next. Easiest to debug.
Example: SEO article from a keywordRouter
Classify first, then hand off to a specialist step.
Example: Support triage botParallel
Independent checks run at once and are merged.
Example: Pull request review teamOrchestrator–workers
A lead agent plans, spawns subagents, then synthesizes.
Example: Competitor research briefEvaluator–optimizer
A grader scores the draft and sends it back until it passes.
Example: SEO article from a keywordHuman approval
The run pauses for a person before anything leaves.
Example: Support triage bot
Bots
Put a workflow where your team already talks
A bot is a workflow with a trigger. The support triage template reads each new message, routes it, drafts a reply and waits for a person to approve before it sends.
- Slack
- Discord
- Telegram
- Microsoft Teams
- GitHub
- Website widget
- TriggerNew message in #support
- RouterClassify the ticket
- Billing
- Bug
- How-to
- AgentDraft the reply
- ApprovalAgent approves
- OutputReply in thread
Dana (customer)
I was charged twice for October and the export button does nothing.Triage bot
Routed: Billing + Bug · reply drafted · waiting for approvalTriage bot → @on-call
“Sorry about that, Dana. I can see two October charges and I’ve asked billing to review them today. For the export button, could you tell me your browser and send a screenshot?”ApproveEditRejectSam (on-call)
Approved ✅
Where it runs
Run it here, or take it with you
Paste into a chat
Every workflow also exports as one prompt for ChatGPT, Claude or Gemini. Parallel steps run in turn; approvals become “wait for my OK”.
Run in your coding agent
Export as SKILL.md and drop it in .claude/skills or .agents/skills. Claude Code and Codex run parallel steps as real subagents.
Share as a pack
Push the skills to GitHub and anyone can install them with npx skills add, or bundle them as a Claude Code plugin.
Run it here with Claude
Sign in and press Run with Claude: each step runs on our servers, with web research, approvals and a full run history.