# Agents Get Started

Use when a developer wants to create a new agent project or get started with AgentCore.

- Repository: https://github.com/aws/agent-toolkit-for-aws (3366 stars)
- Category: AI and agents
- License: Apache-2.0
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add aws/agent-toolkit-for-aws --skill agents-get-started -g -a claude-code -y`
Codex: `npx skills add aws/agent-toolkit-for-aws --skill agents-get-started -g -a codex -y`
Cursor: `npx skills add aws/agent-toolkit-for-aws --skill agents-get-started -g -a cursor -y`
Gemini CLI: `npx skills add aws/agent-toolkit-for-aws --skill agents-get-started -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add aws/agent-toolkit-for-aws`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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 create` and 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-build` or `agents-connect`
- Migrating an existing Bedrock Agent → use `agents-build` (loads [`references/migrate.md`](../agents-build/references/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

```bash
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 the `agents-debug` skill (which loads [`references/doctor.md`](../agents-debug/references/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:

The rest: https://github.com/aws/agent-toolkit-for-aws/blob/HEAD/plugins/aws-agents/skills/agents-get-started/SKILL.md