Agentcore
Run agent-browser on AWS Bedrock AgentCore cloud browsers. Use when the user wants to use AgentCore, run browser automation on AWS, use a cloud browser with AWS credentials, or needs a managed browser session backed by AWS infrastructure. Triggers include "use agentcore", "run on AWS", "cloud browser with AWS", "bedrock browser", "agentcore session", or any task requiring AWS-hosted browser automation.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Agentcore when an AI agent needs a reusable SKILL.md workflow for this job: Run agent-browser on AWS Bedrock AgentCore cloud browsers. Use when the user wants to use AgentCore, run browser automation on AWS, use a cloud browser with AWS credentials, or needs a managed browser session backed by AWS infrastructure. Triggers include "use agentcore", "run on AWS", "cloud browser with AWS", "bedrock browser", "agentcore session", or any task requiring AWS-hosted browser automation.
When not to use it
Skip Agentcore when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/agentcore # Save SKILL.md to ~/.claude/skills/agentcore/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/agentcore/SKILL.md. For a shared project, commit the folder at .claude/skills/agentcore/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Agentcore skill for this task: Use Agentcore when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
70/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 70/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# AWS Bedrock AgentCore
Run agent-browser on cloud browser sessions hosted by AWS Bedrock AgentCore. All standard agent-browser commands work identically; the only difference is where the browser runs.
## Setup
Credentials are resolved automatically:
1. Environment variables (`AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, optionally `AWS_SESSION_TOKEN`) 2. AWS CLI fallback (`aws configure export-credentials`), which supports SSO, IAM roles, and named profiles
No additional setup is needed if the user already has working AWS credentials.
## Core Workflow
```bash # Open a page on an AgentCore cloud browser agent-browser -p agentcore open https://example.com
# Everything else is the same as local Chrome agent-browser snapshot -i agent-browser click @e1 agent-browser screenshot page.png agent-browser close ```
## Environment Variables
| Variable | Description | Default | |----------|-------------|---------| | `AGENTCORE_REGION` | AWS region | `us-east-1` | | `AGENTCORE_BROWSER_ID` | Browser identifier | `aws.browser.v1` | | `AGENTCORE_PROFILE_ID` | Persistent browser profile (cookies, localStorage) | (none) | | `AGENTCORE_SESSION_TIMEOUT` | Session timeout in seconds | `3600` | | `AWS_PROFILE` | AWS CLI profile for credential resolution | `default` |
## Persistent Profiles
Use `AGENTCORE_PROFILE_ID` to persist browser state across sessions. This is useful for maintaining login sessions:
```bash # First run: log in AGENTCORE_PROFILE_ID=my-app agent-browser -p agentcore open https://app.example.com/login agent-browser snapshot -i agent-browser fill @e1 "[email protected]" agent-browser fill @e2 "password" agent-browser click @e3 agent-browser close
# Future runs: already authenticated AGENTCORE_PROFILE_ID=my-app agent-browser -p agentcore open https://app.example.com/dashboard ```
## Live View
When a session starts, AgentCore prints a Live View URL to stderr. Open it in a browser to watch the session in real time from the AWS Console:
``` Session: abc123-def456 Live View: https://us-east-1.console.aws.amazon.com/bedrock-agentcore/browser/aws.browser.v1/session/abc123-def456# ```
## Region Selection
```bash # Default: us-east-1 agent-browser -p agentcore open https://example.com
# Explicit region AGENTCORE_REGION=eu-west-1 agent-browser -p agentcore open https://example.com ```
## Credential Patterns
```bash # Explicit credentials (CI/CD, scripts) export AWS_ACCESS_KEY_ID=AKIA... export AWS_SECRET_ACCESS_KEY=... agent-browser -p agentcore open https://example.com
# SSO (interactive) aws sso login --profile my-profile AWS_PROFILE=my-profile agent-browser -p agentcore open https://example.com
# IAM role / default credential chain agent-browser -p agentcore open https://example.com ```
## Using with AGENT_BROWSER_PROVIDER
Set the provider via environment variable to avoid passing `-p agentcore` on every command:
```bash export AGENT_BROWSER_PROVIDER=agentcore export AGENTCORE_REGION=us-east-2
agent-browser open https://example.com agent-browser snapshot -i agent-browser click @e1 agent-browser close ```
## Common Issues
**"Failed to run aws CLI"** means AWS CLI is not installed or not in PATH. Either install it or set `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` directly.
**"AWS CLI failed: ... Run 'aws sso login'"** means SSO credentials have expired. Run `aws sso login` to refresh them.
**Session timeout:** The default is 3600 seconds (1 hour). For longer tasks, increase with `AGENTCORE_SESSION_TIMEOUT=7200`.
Intended uses
- Use Agentcore when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.