agents-get-started

Guides developers from zero to a deployed agent on AWS AgentCore.

1|Updated Aug 1, 2024
One-click install
npx skills add https://github.com/obispobruno/dotfiles --skill agents-get-started-obispobruno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agents-get-started
Source: https://github.com/obispobruno/dotfiles/tree/main/dot_agents/skills/agents-get-started
Command: npx skills add https://github.com/obispobruno/dotfiles --skill agents-get-started-obispobruno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Starting a new agent project on AWS involves many decisions — framework choice, project scaffolding, local development, and first deployment. This Skill walks developers through the entire journey from "I want to build an agent" to a running, deployed agent on Amazon Bedrock AgentCore, eliminating guesswork about CLI flags, naming rules, and framework trade-offs. ## Core Features & Use Cases - Framework Selection Guidance: Compares Strands, LangGraph, Google ADK, and OpenAI Agents with decision criteria, plus a BYO Container path for unsupported frameworks and languages like Java, TypeScript, or Go. - Project Scaffolding: Constructs and validates the agentcore create command, including project name rules (max 23 alphanumeric characters), protocol, build type, model provider, and memory options. - Local Dev and First Deploy: Explains agentcore dev port behavior, local limitations (no memory or gateway URLs), and walks through agentcore deploy and agentcore invoke. - Use Case: A developer says "build a customer support agent." The Skill recommends Strands with Bedrock, validates the project name, presents the create command for confirmation, explains the generated main.py structure, and guides the first deploy. ## Quick Start Ask the assistant to help you create a new AgentCore agent project, optionally naming a framework like Strands or LangGraph.

Frequently Asked Questions about agents-get-started

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new agent project with AgentCore?▼

Run agentcore create with a name, framework, model provider, build type, and memory option, or use --defaults for Strands with Bedrock. Project names must be alphanumeric, start with a letter, and be at most 23 characters.

Strands vs LangGraph: which framework should I choose for AgentCore?▼

Choose Strands for an AWS-native path with the tightest AgentCore integration, or LangGraph for complex graph-based workflows and existing LangChain investment. Google ADK and OpenAI Agents suit teams already using those SDKs.

Can I use CrewAI or a custom framework with AgentCore?▼

Yes, via the BYO Container path. AgentCore Runtime accepts any container implementing the HTTP contract (POST /invocations, GET /ping). Register your code with agentcore add agent --type byo --build Container and provide a Dockerfile.

What port does the agentcore dev server use?▼

The dev server defaults to port 8080 for HTTP, 8000 for MCP, and 9000 for A2A. If the port is occupied, the CLI auto-increments, so read the actual port from the CLI output or pin it with agentcore dev --port.

Why is my agentcore create command failing on the project name?▼

The CLI rejects names over 23 characters, names with hyphens, underscores, or spaces, and names not starting with a letter. Validate the name before running the command because the CLI error appears late in the flow.

What are the limitations of agentcore dev for local development?▼

Memory and gateway URLs are unavailable locally because both require a deploy. The scaffolded MCP client points at a public example endpoint, and repointing it to a gateway env var before deploying silently yields zero MCP tools.