Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →majiayu000/managed-agent
Run an Anthropic Claude Managed Agent — a cloud agent harness (container + filesystem + tools), the cloud counterpart of the local wasm-agent runtime
Passed 16 of 19 test cases with the skill, and 4 of 19 without it.
and 13 more in the full report
13 fixed5 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
When dispatching a prompt via the cloud agent prompt tool, what is the default timeout in seconds before polling stops, and what is the maximum allowed upper bound for maxWaitMs?
| Checked | Without skill | With skill |
|---|---|---|
| States the default polling wait time is 180 seconds. | Missed | Passed |
| States the maximum capped wait time is 600 seconds. | Passed | Passed |
The instructions your model reads when the skill loads.
ruflo-agent has two agent runtimes behind one mental model:
| Runtime | Tools | Use it when |
|---|---|---|
WASM (local, rvagent) | wasm_agent_* / wasm_gallery_* | fast, free, ephemeral, offline, untrusted code in a sandbox |
| Managed (Anthropic cloud) | managed_agent_* (this skill) | long-running / async work (minutes–hours), a real cloud container with pre-installed packages + network, persistent filesystem + transcript across turns |
This skill drives the managed runtime — Anthropic's Claude Managed Agents (beta). The model: Agent (model + system + tools + MCP servers + skills) → Environment (container template) → Session (running instance) → Events (turns / tool-use / status, persisted server-side). See docs/adr/0001-wasm-contract.md and project ADR-115.
ANTHROPIC_API_KEY (or CLAUDE_API_KEY) in the environment, with Claude Managed Agents beta access.managed_agent_* tool returns a structured "use wasm_agent_create for a local no-key runtime" error — fall back to the WASM skill.Create — mcp__claude-flow__managed_agent_create
{ model?, system?, name?, networking?, packages?, initScript?, mcpServers?, skills? }
→ { sessionId, agentId, environmentId, status }. Provisions Agent + Environment + Session. Save the three ids.
mcpServers: [{type:"url", url, name, authorization_token?}] — the cloud agent must be able to reach the URL. A local ruflo mcp start is not reachable from Anthropic's cloud; deploy/tunnel an HTTP ruflo MCP server first if you want the cloud agent to have ruflo's tools.packages: {pip?:[], npm?:[], apt?:[], cargo?:[], gem?:[], go?:[]} — installed in the container.Prompt — mcp__claude-flow__managed_agent_prompt
{ sessionId, message, maxWaitMs? } → sends a user turn, polls the event log until the session goes idle (default 180s, capped 600s) → { finished, status, stopReason, assistantText, toolUses[], eventCount }. For very long tasks, raise maxWaitMs or follow up with managed_agent_events.
Inspect — mcp__claude-flow__managed_agent_status { sessionId } (idle/running/error) · mcp__claude-flow__managed_agent_events { sessionId, raw? } (full transcript: user turns, agent thinking, tool_use, tool_result, status — the cloud counterpart of wasm_agent_files).
List — mcp__claude-flow__managed_agent_list { limit? } — every session on the org (so you can see which are still running / billing).
Terminate — mcp__claude-flow__managed_agent_terminate { sessionId, environmentId? } — always do this when done: a cloud session keeps billing container time + tokens until deleted. Pass environmentId to also delete the environment ruflo created.
cost-tracking namespace.managed_agent_list then managed_agent_terminate anything stale.managed-agents-2026-04-01); multiagent / define-outcomes on the agent config are research preview.test cases passed, vs 4 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.