Agents Get Started
Use when a developer wants to create a new agent project or get started with AgentCore.
Install
npx skills add aws/agent-toolkit-for-aws --skill agents-get-started -g -a claude-code -y- Repository
- aws/agent-toolkit-for-aws3.4k
- Category
- AI and agents
- Updated
- 5d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Use when a developer wants to create a new agent project or get started with AgentCore. Handles framework selection, project scaffolding, first deploy, and first invocation. Triggers on: "build an agent", "create an agent", "get started", "new project", "agentcore create", "which framework", "Strands vs LangGraph", "hello world agent", "first agent", "create MCP server", "host MCP server", "agentcore dev", "dev server", "what port", "local development". Not for adding capabilities to existing projects, use agents-build or agents-connect. Strands vs LangGraph in a migration context routes to agents-build, not here. Connecting to an existing MCP server routes to agents-connect, not here.
get-started
Walk a developer from zero to a running agent on AWS.
When to use
- Developer wants to build an agent on AWS and doesn't know where to start
- Developer wants to create a new AgentCore project
- Developer is choosing between frameworks (Strands, LangGraph, GoogleADK, OpenAI Agents)
- Developer just ran
agentcore createand wants to know what to do next
Do NOT use for:
- Environment/prerequisite issues (CLI not found, credentials broken) → use
agents-debug - Adding capabilities to an existing project (memory, tools, policies) → use
agents-buildoragents-connect - Migrating an existing Bedrock Agent → use
agents-build(loadsreferences/migrate.md)
Input
$ARGUMENTS can be:
- A framework preference: "using LangGraph", "with Strands"
- A protocol: "MCP server", "A2A"
- A description of what the agent should do: "a customer support agent"
- Empty, the skill will guide framework selection
Process
Step 0: Verify CLI version
agentcore --version
This skill requires v0.9.0 or later.
If the version is older:
Your AgentCore CLI is out of date (found vX.Y.Z, need v0.9.0+).
Offer to run the update: agentcore update. After the update completes, re-check the version to confirm it's ≥0.9.0 before continuing. Preserve any context the developer already provided (framework preference, project name, what they want to build) so they don't have to repeat themselves.
If agentcore is not found:
The AgentCore CLI isn't installed. Run
npm install -g @aws/agentcore(requires Node.js 20+). If you're having trouble with installation, I can run theagents-debugskill (which loadsreferences/doctor.md) to diagnose your environment.
Step 1: Determine intent, exploring or ready to create?
Before jumping into framework selection, figure out where the developer is:
