Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Deploy production LangGraph agents on AWS Bedrock AgentCore. Use for (1) multi-agent systems with orchestrator and specialist agent patterns, (2) building stateful agents with persistent cross-session memory, (3) connecting external tools via AgentCore Gateway (MCP, Lambda, APIs), (4) managing shared context across distributed agents, or (5) deploying complex agent ecosystems via CLI with production observability and scaling.
Deploy production LangGraph agents on AWS Bedrock AgentCore. Use for (1) multi-agent systems with orchestrator and specialist agent patterns, (2) building stateful agents with persistent cross-session memory, (3) connecting external tools via AgentCore Gateway (MCP, Lambda, APIs), (4) managing shared context across distributed agents, or (5) deploying complex agent ecosystems via CLI with production observability and scaling.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Multi-agent systems on AWS Bedrock AgentCore with LangGraph orchestration. Source: https://github.com/aws/bedrock-agentcore-starter-toolkit
pip install bedrock-agentcore bedrock-agentcore-starter-toolkit langgraph uv tool install bedrock-agentcore-starter-toolkit # installs agentcore CLI
from langgraph.graph import StateGraph, START from langgraph.graph.message import add_messages from langgraph.prebuilt import ToolNode, tools_condition # routing + tool execution from bedrock_agentcore.runtime import BedrockAgentCoreApp from typing import Annotated from typing_extensions import TypedDict class State(TypedDict): messages: Annotated[list, add_messages] builder = StateGraph(State) builder.add_node("agent", agent_node) builder.add_node("tools", ToolNode(tools)) # prebuilt tool executor builder.add_conditional_edges("agent", tools_condition) # routes to tools or END builder.add_edge(START, "agent") graph = builder.compile() app = BedrockAgentCoreApp() # Wraps as HTTP service on port 8080 (/invocations, /ping) @app.entrypoint def invoke(payload, context): result = graph.invoke({"messages": [("user", payload.get("prompt", ""))]}) return {"result": result["messages"][-1].content} app.run()
CommandPurposeagentcore configure -e agent.py --region us-east-1Setupagentcore configure -e agent.py --region us-east-1 --name my_agent --non-interactiveScripted setupagentcore launch --deployment-type containerDeploy (container mode)agentcore launch --disable-memoryDeploy without memory subsystemagentcore devHot-reload local dev serveragentcore invoke '{"prompt": "Hello"}'Testagentcore destroyCleanup
Orchestrator delegates to specialists (customer service, e-commerce, healthcare, financial, etc.) Specialists: inline functions or separate deployed agents; all share session_id for context
from bedrock_agentcore.memory import MemoryClient memory = MemoryClient() memory.create_event(session_id, actor_id, event_type, payload) # Store events = memory.list_events(session_id) # Retrieve (returns list) STM: Turn-by-turn within session | LTM: Facts/decisions across sessions/agents ~10s eventual consistency after writes
python -m bedrock_agentcore.gateway.deploy --stack-name my-agents --region us-east-1 from bedrock_agentcore.gateway import GatewayToolClient gateway = GatewayToolClient() result = gateway.call("tool_name", param1=value1, param2=value2) Transport: Fallback Mock (local), Local MCP servers, Production Gateway (Lambda/REST/MCP) Auto-configures BEDROCK_AGENTCORE_GATEWAY_URL after deploy
Multiple agents coordinating? β Orchestrator + specialists pattern Persistent cross-session memory? β AgentCore Memory (not LangGraph checkpoints) External APIs/Lambda? β AgentCore Gateway Single agent, simple? β Quick Start above Complex multi-step logic? β StateGraph + tools_condition + ToolNode
AgentCore Runtime: HTTP service on port 8080 (handles /invocations, /ping) AgentCore Memory: Managed cross-session/cross-agent memory LangGraph Routing: tools_condition for agentβtool routing, ToolNode for execution AgentCore Gateway: Transforms APIs/Lambda into MCP tools with auth
Start with letter, only letters/numbers/underscores, 1-48 chars: my_agent not my-agent
IssueFixon-demand throughput isn't supportedUse us.anthropic.claude-* inference profilesModel use case details not submittedFill Anthropic form in Bedrock ConsoleInvalid agent nameUse underscores not hyphensMemory empty after writeWait ~10s (eventual consistency)Container not reading .envSet ENV in Dockerfile, not .envMemory not working after deployCheck logs for "Memory enabled/disabled"list_events returns emptyCheck actor_id/session_id match; event['payload'] is a listGateway "Unknown tool"Lambda must strip ___ prefix from bedrockAgentCoreToolNamePlatform mismatch warningNormal - CodeBuild handles ARM64 cross-platform builds
agentcore-cli.md - CLI commands, deployment, lifecycle agentcore-runtime.md - Streaming, async, observability agentcore-memory.md - STM/LTM patterns, API reference agentcore-gateway.md - Tool integration, MCP, Lambda langgraph-patterns.md - StateGraph design, routing reference-architecture-advertising-agents-use-case.pdf - Example multi-agent architecture
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.