aws-skills — Claude Code skill: AWS infrastructure planning and review
Plans and reviews AWS architecture and infrastructure changes before an agent touches anything in your cloud account.
MIT ★ 50,109 updated 2026-10-29
npx skills add sickn33/agentic-awesome-skills --skill aws-skills -a claude-codeWhat aws-skills does
The skill walks an agent through a short sequence. It starts with the application's requirements, the AWS services already in use, the target account and region, and the project's own infrastructure files. From there it points the agent at the external zxkane/aws-skills collection and picks the workflow that matches your services. That collection lives in a separate repository rather than inside this skill.
You get back a plan: resource boundaries, IAM access, networking, cost assumptions, plus a way to validate the change and roll it back. Proposed changes stay separate from what was actually observed. Anything that creates, modifies or deletes cloud resources waits for your approval.
The upstream repository is a hard prerequisite. If it can't be read, or you can't supply authorized read-only inventory or your own configuration, the skill stops instead of guessing at your account.
What it helps with
- draft an AWS change plan before anything is deployed
- map IAM permissions and resource boundaries for an existing service
- pick the right workflow from the collection for your services and framework
- work out validation and rollback ahead of a cloud change
- separate observed configuration from proposed edits
Example prompts for the agent
- Review this project's AWS infrastructure, read the configuration first, then propose a least-privilege plan without deploying.
- Draft a change plan for this service: resource boundaries, IAM, networking, cost assumptions and rollback.
- Check the plan before we touch the cloud, and tell me which checks can run without account access.
How to install aws-skills
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill aws-skills -a claude-code2Manually: put the files in place
~/.claude/skills/aws-skills/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/aws-skills/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill aws-skills -a codex2Manually: put the files in place
.agents/skills/aws-skills/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill aws-skills -a cursor2Manually: put the files in place
.cursor/skills/aws-skills/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sickn33/agentic-awesome-skills skills/aws-skills2Manually: put the files in place
.github/skills/aws-skills/SKILL.md1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill aws-skills -a gemini-cli2Platform CLI
gemini skills install https://github.com/sickn33/agentic-awesome-skills --path skills/aws-skillsManually: put the files in place
.devin/skills/aws-skills/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill aws-skills -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about aws-skills
How do I install aws-skills in Claude Code?
Run npx skills add sickn33/agentic-awesome-skills --skill aws-skills -a claude-code; the skill then sits at ~/.claude/skills/aws-skills/SKILL.md.
What does aws-skills do?
It routes an agent through AWS planning and review: read the project's infrastructure, choose a matching workflow from the external collection, then return a plan covering IAM, networking, cost and rollback.
Does aws-skills deploy anything?
No. It produces and reviews a plan, and every create, modify or delete needs your authorized scope and the project's deployment controls. A plan alone doesn't prove the deployment works.
Source text
SKILL.md · MIT
--- name: aws-skills description: "Plan and review AWS architecture and infrastructure changes using the upstream AWS skill collection." risk: safe source: "https://github.com/zxkane/aws-skills" date_added: "2026-02-27" --- # AWS Skill Collection Workflow ## When to Use - You need to choose an AWS architecture or infrastructure workflow for an existing application. - You want to review an infrastructure plan before any cloud change. ## Workflow 1. Establish the application requirements, existing AWS services, target account/region, constraints, and required outcome. Read the project's infrastructure definitions before proposing changes. 2. Open the [upstream AWS skill collection](https://github.com/zxkane/aws-skills) and select the workflow matching the actual services and infrastructure framework. This catalog entry is a routing workflow; it does not bundle every upstream skill. 3. Read that workflow's prerequisites and referenced documentation. For an existing deployment, request authorized read-only inventory or use user-provided configuration; do not infer account identity from names. 4. Produce an architecture or infrastructure plan with resource boundaries, IAM access, networking, cost assumptions, and a validation/rollback plan. Distinguish observed configuration from proposed changes. 5. Review the plan with the user before any operation that creates, modifies, or deletes cloud resources. Follow the selected tool's current documentation and the project's normal review/deployment process. 6. Verify the result against the requested requirements and report which checks ran, which were simulated, and which require deployment access. ## Example > Review this application's AWS infrastructure and propose a least-privilege change plan. Read configuration first; do not deploy. ## Limitations - The upstream collection is an external prerequisite; report inaccessible guidance instead of inventing its instructions. - Planning does not prove a deployment works. Never claim account, pricing, permissions, or availability without current evidence. - Cloud changes require the user's authorized scope and the project's deployment controls.
© sickn33 · MIT · sickn33/agentic-awesome-skills