AWS Serverless Eda
zxkane/aws-skills
AWS serverless and event-driven architecture expert based on Well-Architected Framework.
Builds, deploys, manages, debugs, configures, and optimizes serverless applications on AWS using Lambda, API Gateway, Step Functions, EventBridge, and SAM/CDK.
Install AWS Serverless
$ npx skills add aws/agent-toolkit-for-aws --skill aws-serverless -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aws/agent-toolkit-for-aws aws-serverless --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/core-skills/aws-serverless .claude/skills/aws-serverless && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "aws-serverless" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/core-skills/aws-serverless into .claude/skills/aws-serverless/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aws-serverless", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/core-skills/aws-serverlessType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add aws/agent-toolkit-for-aws --skill aws-serverless -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aws/agent-toolkit-for-aws aws-serverless --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/core-skills/aws-serverless .agents/skills/aws-serverless && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "aws-serverless" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/core-skills/aws-serverless into .agents/skills/aws-serverless/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aws-serverless", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aws/agent-toolkit-for-aws --skill aws-serverless -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aws/agent-toolkit-for-aws aws-serverless --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/core-skills/aws-serverless .cursor/skills/aws-serverless && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "aws-serverless" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/core-skills/aws-serverless into .cursor/skills/aws-serverless/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aws-serverless", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/aws/agent-toolkit-for-aws.git --path skills/core-skills/aws-serverless--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add aws/agent-toolkit-for-aws --skill aws-serverless -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aws/agent-toolkit-for-aws aws-serverless --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/core-skills/aws-serverless .gemini/skills/aws-serverless && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "aws-serverless" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/core-skills/aws-serverless into .gemini/skills/aws-serverless/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aws-serverless", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install aws/agent-toolkit-for-aws aws-serverlessInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add aws/agent-toolkit-for-aws --skill aws-serverless -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/core-skills/aws-serverless .github/skills/aws-serverless && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "aws-serverless" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/core-skills/aws-serverless into .github/skills/aws-serverless/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aws-serverless", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aws/agent-toolkit-for-aws --skill aws-serverless -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aws/agent-toolkit-for-aws aws-serverless --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/core-skills/aws-serverless .opencode/skills/aws-serverless && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "aws-serverless" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/core-skills/aws-serverless into .opencode/skills/aws-serverless/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "aws-serverless", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
aws-serverless- GitHub stars
- 2.8k
- Token cost
- ~2.5k tokens
- SKILL.md length
- 1,013 words
- Files
- 11 (incl. references, assets)
- Skills in repo
- 138
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Builds, deploys, manages, debugs, configures, and optimizes serverless applications on AWS using Lambda, API Gateway, Step Functions, EventBridge, and SAM/CDK.
- Mentions of Lambda
- SKILL.md covers Specialized skills — check… and Routing (general references in…
- Runs Python scripts from its folder
- CDK serverless stacks
What it does
AWS Serverless is an agent skill from aws/agent-toolkit-for-aws, published by the product's own GitHub organization. Builds, deploys, manages, debugs, configures, and optimizes serverless applications on AWS using Lambda, API Gateway, Step Functions, EventBridge, and SAM/CDK. Covers cold starts, CORS debugging, event source mappings, troubleshooting, concurrency, SnapStart, Powertools, function URLs, EventBridge Scheduler, Lambda layers, and production readiness. Triggers on mentions of Lambda, API Gateway, Step Functions, SAM templates, CDK serverless stacks, DynamoDB stream triggers, SQS event sources, cold starts, timeouts…
Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including reference files and assets (for example `assets/powertools-handler.py`, `references/api-gateway.md` and `references/architecture.md`).
It sits in Backend & APIs, covering Serverless, Microservices and Event-driven systems. It works with Amazon Web Services, Amazon DynamoDB and AWS Lambda. The repository describes itself as: Official, AWS-supported MCP servers, skills, and plugins to help AI agents build on AWS. The licence is Apache-2.0.
When your agent uses it
- Mentions of Lambda
- CDK serverless stacks
- DynamoDB stream triggers
- SQS event sources
Example prompts
- “serverless.”
- “/aws-serverless”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit bd49cc8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships script files (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
docs.aws.amazon.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
AWS Serverless loads about 2.5k tokens when it runs, and up to ~19k if it reads all its reference files. Until then it costs about 184 tokens; SKILL.md has 1,013 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from aws/agent-toolkit-for-aws at commit bd49cc8, republished under its Apache-2.0 licence (© aws). 1,013 words, ~2,461 tokens.
Download SKILL.mdSave it as
.claude/skills/aws-serverless/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.- name
- aws-serverless
- description
- Builds, deploys, manages, debugs, configures, and optimizes serverless applications on AWS using Lambda, API Gateway, Step Functions, EventBridge, and SAM/CDK. Covers cold starts, CORS debugging, event source mappings, troubleshooting, concurrency, SnapStart, Powertools, function URLs, EventBridge Scheduler, Lambda layers, and production readiness. Triggers on mentions of Lambda, API Gateway, Step Functions, SAM templates, CDK serverless stacks, DynamoDB stream triggers, SQS event sources, cold starts, timeouts, 502/504 errors, throttling, concurrency, CORS, Powertools, or any event-driven architecture on AWS, even without the word "serverless." Does not apply to EC2, ECS/Fargate containers, or Amplify hosting.
- metadata.version
- 4
AWS Serverless
Domain expertise for building serverless applications on AWS: Lambda, API Gateway, Step Functions, EventBridge, event source mappings, concurrency, cold starts, deployment, and troubleshooting.
Works best with the AWS MCP server — run CLI commands, query CloudWatch, validate configs directly. All guidance also works with standard AWS CLI access.
Specialized skills — check these first
These cover capabilities and procedures the general references below do not. Several are specialized features or step-by-step tested procedures you would otherwise miss. Route to the matching skill before falling back to the references.
Advanced Lambda compute (easy to overlook)
| Use this skill | When the workload involves |
|---|---|
| aws-lambda-microvms | Strong tenant isolation, sandboxed/untrusted code execution (AI agent code sandboxes, REPLs, notebooks, CI runners), long-lived sessions, suspend/resume with preserved state, port-listening servers (gRPC, WebSocket, custom TCP), Firecracker microVMs, snapshot-resumable compute, up to 8-hour lifetimes |
| aws-lambda-durable-functions | Durable execution, checkpoint-and-replay, long-running multi-step workflows written as plain code (TS/Python/Java), automatic state persistence, saga pattern in code, human-in-the-loop callbacks, executions up to 1 year, context.step/context.wait/context.invoke, withDurableExecution, durable-execution-sdk |
| aws-lambda-managed-instances | Lambda Managed Instances (LMI), capacity providers, EC2-backed Lambda, steady high-volume traffic (50M+ req/mo) wanting Savings Plans / Reserved Instance pricing, PerExecutionEnvironmentMaxConcurrency, CapacityProviderConfig, multi-concurrent execution environments |
Workflow orchestration
Route here when the user wants to coordinate multiple steps, services, or functions. Triggers include "orchestration", "workflow", "state machine", "multi-step coordination", "coordinate Lambda functions", "durable execution", "pipeline with retries", or intent to build saga/compensation, human-in-the-loop approval, fan-out, or long-running async coordination.
When starting a new orchestration or multi-step workflow, you MUST surface the choice between AWS Step Functions and AWS Lambda Durable Functions before implementing — do not silently pick one. Route on the signals below. When the request names only a generic pattern (saga/compensation, human-in-the-loop, fan-out, or "workflow orchestration") with no technology, present both options and the one-line tradeoff, then let the user decide. Do not lead with the tradeoff caveats when the signals already point to one service.
| Use this skill | When the workload involves |
|---|---|
| aws-step-functions | Orchestration whose primary work is calling AWS services directly; coordinating non-Lambda compute (ECS/Fargate, Glue, SageMaker, Batch) through native managed integrations; a visual, auditable workflow definition required for compliance, cross-team operational observability, or as a shared contract between teams that do not share a codebase (ASL is the specification, not application code); authoring or editing state machines and Amazon States Language (ASL) — state types, JSONata data transformation, Retry/Catch error handling, .sync/waitForTaskToken service integrations, Distributed Map, TestState unit testing, JSONPath-to-JSONata migration |
| aws-lambda-durable-functions | Code-first orchestration in-process when already building on Lambda (context.step/context.wait/context.invoke, withDurableExecution); many fine-grained steps per execution where cumulative Step Functions Standard state-transition cost may be significant — compare Step Functions pricing (Standard vs Express) against Lambda invocation cost at the expected volume before choosing; orchestration steps written in a general-purpose language within the same application codebase (share modules, data types, and test suites with application code); teams applying standard software-engineering practices (unit tests, code review, type checking) to orchestration logic without learning a declarative workflow language |
Tradeoff (use when either fits): Durable Functions keeps orchestration in your Lambda codebase; Step Functions externalizes it into a managed, visual state machine with built-in service integrations.
Security: Both services persist workflow state and payloads — Step Functions records full input/output in execution history (viewable in the console and, if logging is enabled, CloudWatch Logs). As a baseline, enable execution logging (CloudTrail) and CloudWatch alarms on execution failures, and use least-privilege per-workflow execution roles. Do not pass secrets, tokens, or PII through workflow state; reference them by Secrets Manager/ARN pointer, and apply a customer-managed KMS key to encrypt state when the data is sensitive.
Show full SKILL.md (427 more words)Show less
Event-driven architectures
Route here when the user is designing or operating an event-driven system rather than orchestrating a known sequence of steps. Triggers include "event bus", "event-driven architecture", "pub/sub", "publish/subscribe", "fan-out", "event ordering", "ordered delivery", "FIFO events", "event replay", "replay events", "event retention", "event store", "CloudEvents", "Avro", "Protobuf", "schema registry", "deduplication", "choreography", "decoupling", "asynchronous integration", "event broker", or a central bus shared across teams and accounts.
| Use this skill | When the workload involves |
|---|---|
| amazon-eventbridge-event-bus | A new event-driven workload; a platform team owning a central bus that many teams and accounts publish to and subscribe from; governance of that bus (subscriber control, revocation, per-account throttling, cost allocation, end-to-end observability); open event formats (Avro, Protobuf, CloudEvents) decoded through a schema registry; ordered or FIFO delivery per event group; high fan-out where per-account forwarding cost matters; durable retention and replay of past events into a newly created subscriber; per-subscriber JSONata transformation; deduplication; choreography and decoupling across services; event-driven architecture spanning multiple accounts. This skill MUST NOT be used for questions regarding the EventBridge classic custom event bus, EventBridge Scheduler, EventBridge Pipes, EventBridge Global Endpoints, the EventBridge Schema Registry, EventBridge API Destinations, or EventBridge Connections. |
Step-by-step task procedures (tested CLI SOPs)
| Use this skill | For the task |
|---|---|
| connecting-lambda-to-api-gateway | Wire an existing Lambda to a new REST/HTTP API: proxy integration, permissions, CORS, throttling, access logging, deployment |
| connecting-lambda-to-dynamodb | Connect Lambda to DynamoDB: IAM execution role, read/write permissions, stream event source mapping |
| creating-api-gateway-stage | Create an API Gateway stage with CloudWatch logging, X-Ray tracing, throttling, WAF association, and authorization |
| deploying-custom-domain-rest-api | Deploy a Regional REST API with custom domain: ACM cert, Lambda backend, request authorizer, base path mapping, Route 53 DNS |
| debugging-lambda-timeouts | Systematically diagnose a timing-out Lambda: config, CloudWatch logs/metrics, VPC, cold starts, memory, downstream calls |
| processing-s3-uploads-with-step-functions | Deploy an event-driven workflow: S3 upload → EventBridge → Step Functions → Lambda (small files) or Fargate (large files), with VPC/ECR/ECS/IAM |
Routing (general references in this skill)
| User need | Read |
|---|---|
| Building a new serverless app — pattern selection | architecture.md |
| Lambda config, cold starts, SnapStart, memory, VPC, layers, Function URLs | lambda.md |
| Concurrency (reserved, provisioned, ESM controls) | concurrency.md |
| Event sources (SQS, DynamoDB Streams, SNS, Kinesis), filtering, batch failures | event-sources.md |
| Step Functions, EventBridge rules/pipes/scheduler | orchestration.md |
| API Gateway quotas, authorizers, WebSocket | api-gateway.md |
| SAM/CDK resource types and fast iteration | deployment.md |
| Production readiness, observability, anti-patterns | production.md |
| Debugging an error (exact string → cause → fix) | troubleshooting.md |
| Powertools handler template | powertools-handler.py |
Note: Reference files contain specific runtime versions, quotas, and feature matrices that change. When precision matters (production, runtime choice, quotas), confirm against current AWS documentation. The references focus on values and gotchas that are easy to get wrong — not on basics.
© aws, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 10 other files (references, assets) in skills/core-skills/aws-serverless of aws/agent-toolkit-for-aws.
- SKILL.md
- assets/powertools-handler.py
- references/api-gateway.md
- references/architecture.md
- references/concurrency.md
- references/deployment.md
- references/event-sources.md
- references/lambda.md
- references/orchestration.md
- references/production.md
- references/troubleshooting.md
Open the folder on GitHubat commit bd49cc8
Compare with similar skills
AWS Serverless next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| AWS Serverless this skillaws/agent-toolkit-for-aws | 2.8k | — | ~2.5k | Automated safety check: Pass | Apache-2.0 | |
| AWS Serverless Edazxkane/aws-skills | 367 | 4 repos | ~3.2k | Automated safety check: Pass | MIT | |
| AWS Serverlessdavila7/claude-code-templates | 32k | 7 repos | ~2k | Automated safety check: Pass | MIT | |
| AWS Lambdaawslabs/agent-plugins | 912 | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| AWS Lambda Microvmsawslabs/agent-plugins | 912 | 1 repos | ~4.1k | Automated safety check: Pass | Apache-2.0 | |
| AWS Lambda Durable Functionsawslabs/agent-plugins | 912 | — | ~2.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
AWS Serverless
davila7/claude-code-templates
Specialized skill for building production-ready serverless applications on AWS.
- Official
AWS Lambda
awslabs/agent-plugins
Design, build, deploy, test, and debug serverless applications with AWS Lambda.
- Official
AWS Lambda Microvms
awslabs/agent-plugins
Build, run, debug, and operate applications on AWS Lambda MicroVMs — Firecracker-isolated, snapshot-resumable serverless compute environments that run inside a container with up to 8-hour lifetimes.
- Official
AWS Lambda Durable Functions
awslabs/agent-plugins
Build resilient, long-running, multi-step applications with AWS Lambda durable functions with automatic state persistence, retry logic, and orchestration for long-running executions.
- Official
AWS Serverless Deployment
awslabs/agent-plugins
AWS SAM and AWS CDK deployment for serverless applications. An agent skill from awslabs/agent-plugins.
More from aws/agent-toolkit-for-aws
All 138 skills in this repo- Official
Agent Advisor
aws/agent-toolkit-for-aws
Entry point for AI-agent work on AWS: pick a runtime, plan a migration for existing workloads, and build an executable POC — one phased flow.
- Official
Agents Build
aws/agent-toolkit-for-aws
A skill your agent uses to extend an existing agent project with memory, app integration, VPC, multi-agent, migration, model, browser, code interpreter, payments, or resource removal.
- Official
Launch With AWS
aws/agent-toolkit-for-aws
Migrates vibe-coded web applications to AWS. An agent skill from aws/agent-toolkit-for-aws.
- Official
Processing S3 Uploads With Step Functions
aws/agent-toolkit-for-aws
Deploy an event-driven workflow that routes S3 uploads to either Lambda or Fargate via Step Functions based on file size.
- Official
AWS Marketplace Metering
aws/agent-toolkit-for-aws
Deploys, queries, and debugs AWS Marketplace usage-based (PAYG) metering — the pipeline (ResolveCustomer, BatchMeterUsage, EventBridge via SAM) and querying/debugging metering records, statuses…
- Official
Agents Pay
aws/agent-toolkit-for-aws
A skill your agent uses when THIS agent needs to pay for x402-protected content at runtime: hitting a paywall mid-task, settling it via AgentCore Payments, and applying operator-defined spend limits.
Related
Categories
Questions about AWS Serverless
What does AWS Serverless do?
Builds, deploys, manages, debugs, configures, and optimizes serverless applications on AWS using Lambda, API Gateway, Step Functions, EventBridge, and SAM/CDK. AWS Serverless is an agent skill from aws/agent-toolkit-for-aws, published by the product's own GitHub organization. Builds, deploys, manages, debugs, configures, and optimizes serverless applications on AWS using Lambda, API Gateway, Step Functions, EventBridge, and SAM/CDK.
When should I use AWS Serverless?
AWS Serverless fits situations like: mentions of Lambda; CDK serverless stacks; dynamoDB stream triggers; SQS event sources.
How do I install AWS Serverless in Claude Code?
Run `npx skills add aws/agent-toolkit-for-aws --skill aws-serverless -a claude-code`. Or copy the skill folder (skills/core-skills/aws-serverless in aws/agent-toolkit-for-aws) into .claude/skills/aws-serverless in your project. Claude Code loads it when a task matches its description.
How do I install AWS Serverless in Codex?
Run `npx skills add aws/agent-toolkit-for-aws --skill aws-serverless -a codex`. Or copy the skill folder (skills/core-skills/aws-serverless in aws/agent-toolkit-for-aws) into .agents/skills/aws-serverless in your project. Codex loads it when a task matches its description.
Can I use AWS Serverless in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aws/agent-toolkit-for-aws --skill aws-serverless -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/aws-serverless, .gemini/skills/aws-serverless, .github/skills/aws-serverless and .opencode/skills/aws-serverless in your project.
What does AWS Serverless need to run?
Going by SKILL.md and its folder, AWS Serverless needs Python for the scripts in its folder. Our summary lists: Python 3.
Does AWS Serverless access the network?
SKILL.md names 1 domain. As links in the text: docs.aws.amazon.com. This is read from the text; nothing was executed.
Is AWS Serverless safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does AWS Serverless use?
AWS Serverless is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does AWS Serverless use?
About 2.5k tokens (SKILL.md is roughly 9.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 17k tokens, read only when the agent opens those files.
What are the alternatives to AWS Serverless?
Skills that share tags, products or a category with AWS Serverless: AWS Serverless Eda (zxkane/aws-skills, 367 stars), AWS Serverless (davila7/claude-code-templates, 32k stars), AWS Lambda (awslabs/agent-plugins, 912 stars) and AWS Lambda Microvms (awslabs/agent-plugins, 912 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains AWS Serverless?
aws (a GitHub organization, an official publisher) maintains it in aws/agent-toolkit-for-aws, which has 2,816 GitHub stars. The repository holds 138 skills in this directory. The repository was last updated on October 7, 2026.
Source: aws/agent-toolkit-for-aws on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.