Detalle del Skill
agents-get-started
Developer onboarding for AWS agent projects, but platform-specific.
Revisar antes de usar
La revisión automática comprueba relevancia, no seguridad ni respaldo. Lee las instrucciones de la fuente antes de usar este Skill.
SKILL.md
Este extracto es una copia guardada durante la revisión. La fuente externa contiene la versión completa y actual.
--- name: agents-get-started 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. allowed-tools: Read Grep Glob Bash metadata: type: skill version: "1.0.0" author: aws-agentcore requires-cli: ">=0.9.0" --- # 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: **Ask the developer:** "Are you exploring options (comparing frameworks, understanding what AgentCore does) or ready to create a project?" - **Exploring** → Go to Step 2 (framework comparison). Present the options, answer questions, and wait. Do not construct a `create` command until they signal they're ready. - **Ready to create** → Skip to Step 3 (create the project). If they already specified a framework, skip Step 2 entirely. - **Already has a project** → Look for `agentcore/agentcore.json` in the current directory. If found, read it and skip to Step 5 (what to do next). Don't re-scaffold. If the developer's intent is clear from `$ARGUMENTS` (e.g., "create a Strands agent called MyBot"), skip straight to Step 3. ### Step 2: Framework selection **Check conversation context first.** If the developer already discussed frameworks earlier in this conversation (e.g., from a previous skill invocation), don't re-present the full table. Summarize what was discussed and ask if they've decided, or if anything changed. If this is the first time discussing frameworks, present the options: **Supported frameworks (CLI-scaffolded, Python):** | Framework | CLLeer la fuente completa en GitHub (abre una página externa)