Agent skill · DevOps & Cloud

aws-strands-agents-agentcore

Use when working with AWS Strands Agents SDK or Amazon Bedrock AgentCore platform for building AI agents. Provides architecture guidance, implementation patterns, deployment strategies, observability, quality evaluations, multi-agent orchestration, and MCP server integration.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill aws-strands-agents-agentcore --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 12 KB
Bundled scripts: none
Path: skills/agent/aws-strands-agents-agentcore/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# AWS Strands Agents & AgentCore ## Overview **AWS Strands Agents SDK**: Open-source Python framework for building AI agents with model-driven orchestration (minimal code, model decides tool usage) **Amazon Bedrock AgentCore**: Enterprise platform for deploying, operating, and scaling agents in production **Relationship**: Strands SDK runs standalone OR with AgentCore platform services. AgentCore is optional but provides enterprise features (8hr runtime, streaming, memory, identity, observability). --- ## Quick Start Decision Tree ### What are you building? **Single-purpose agent**: - Event-driven (S3, SQS, scheduled) → Lambda deployment - Interactive with streaming → AgentCore Runtime - API endpoint (stateless) → Lambda **Multi-agent system**: - Deterministic workflow → Graph Pattern - Autonomous collaboration → Swarm Pattern - Simple delegation → Agent-as-Tool Pattern **Tool/Integration Server (MCP)**: - **ALWAYS** deploy to ECS/Fargate or AgentCore Runtime - **NEVER Lambda** (stateful, needs persistent connections) See **[architecture.md](references/architecture.md)** for deployment examples. --- ## Critical Constraints ### MCP Server Requirements 1. **Transport**: MUST use `str

What's inside
Steps it walks through
  1. Overview
  2. Quick Start Decision Tree
  3. What are you building?
  4. Critical Constraints
  5. MCP Server Requirements
  6. Tool Count Limits
  7. Token Management
  8. Deployment Decision Matrix
  9. Multi-Agent Pattern Selection
  10. When to Read Reference Files
  11. [patterns.md](references/patterns.md)
  12. [observability.md](references/observability.md)
  13. [evaluations.md](references/evaluations.md)
  14. [limitations.md](references/limitations.md)
Ships with 1 file
  • metadata.json
Commands it runs
aws bedrock list-foundation-models --by-provider anthropic \
export AGENT_OBSERVABILITY_ENABLED=true
export OTEL_PYTHON_DISTRO=aws_distro
export OTEL_RESOURCE_ATTRIBUTES="service.name=my-agent"
opentelemetry-instrument python agent.py
More from claude-skill-registry
All skills →
About this skill
What does the aws-strands-agents-agentcore skill do?

Use when working with AWS Strands Agents SDK or Amazon Bedrock AgentCore platform for building AI agents. Provides architecture guidance, implementation patterns, deployment strategies, observability, quality evaluations, multi-agent orchestration, and MCP server integration.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill aws-strands-agents-agentcore --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going