Aws Skills
Give your coding agent AWS-focused patterns for IaC, service wiring, and cloud architecture when you ship on Amazon Web Services.
Overview
aws-skills is an agent skill most often used in Build (also Ship, Operate) that guides AWS development with infrastructure automation and cloud architecture patterns.
Install
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill aws-skillsWhat is this skill?
- Covers AWS development with infrastructure automation and cloud architecture patterns
- Anchored to the zxkane/aws-skills source repository for deeper examples
- Intended when the task clearly matches AWS scope—not a substitute for account-specific validation
- Risk-marked safe in frontmatter for procedural guidance rather than destructive defaults
- Stops the agent when permissions, inputs, or success criteria are missing
Adoption & trust: 556 installs on skills.sh; 40.1k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need to design or automate on AWS but your agent keeps giving generic cloud advice without IaC discipline or architecture guardrails.
Who is it for?
Solo builders shipping SaaS or APIs on AWS who want a dedicated skill trigger before IAM, networking, or automation tasks.
Skip if: Teams that need a full Terraform/CDK playbook in-repo when this skill only provides scope framing and a link to the source repo.
When should I use this skill?
Use when the task clearly matches AWS development with infrastructure automation and cloud architecture patterns.
What do I get? / Deliverables
After invocation, the agent follows AWS-oriented procedural guidance and defers to environment-specific validation instead of treating chat output as production-ready infra.
- AWS-oriented implementation or design guidance aligned to the stated task scope
- Explicit stop/clarification when permissions or success criteria are missing
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
AWS work usually starts when you integrate cloud services into the product, which is the canonical Build shelf even though the same patterns recur at Ship and Operate. Integrations is the right subphase because the skill centers on connecting apps to AWS APIs, automation, and infrastructure—not generic frontend or PM work.
Where it fits
Wire a new Lambda + API Gateway path before your MVP backend ships.
Double-check launch-time AWS resource layout and automation steps before go-live.
Iterate on existing AWS stacks when scaling or tightening architecture after users land.
How it compares
Use as a scoped AWS context pack—not a replacement for your org’s runbooks, staged applies, or third-party IaC skills with pinned modules.
Common Questions / FAQ
Who is aws-skills for?
aws-skills is for solo and indie developers using AI coding agents who regularly touch Amazon Web Services for integrations, automation, or architecture decisions and want a named skill to bound that work.
When should I use aws-skills?
Use it during Build when wiring AWS services, during Ship when preparing cloud launch paths, and during Operate when adjusting infra—whenever the task clearly matches AWS development, infrastructure automation, or cloud architecture patterns rather than unrelated app code.
Is aws-skills safe to install?
Frontmatter marks the skill as safe procedural guidance, but AWS tasks can still imply privileged operations; review the Security Audits panel on this Prism page and never let an agent apply changes without your account guardrails.
SKILL.md
READMESKILL.md - Aws Skills
# Aws Skills ## Overview AWS development with infrastructure automation and cloud architecture patterns ## When to Use This Skill Use this skill when you need to work with aws development with infrastructure automation and cloud architecture patterns. ## Instructions This skill provides guidance and patterns for aws development with infrastructure automation and cloud architecture patterns. For more information, see the [source repository](https://github.com/zxkane/aws-skills). ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.