- name
Perform an AWS Well-Architected Framework review of the current workload IaC and architecture, generating findings and GitHub issues for improvements.
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add github/awesome-copilot --skill aws-well-architected-review -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add github/awesome-copilot --skill aws-well-architected-review -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add github/awesome-copilot --skill aws-well-architected-review -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add github/awesome-copilot --skill aws-well-architected-review -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/github/awesome-copilot/tree/HEAD/skills/aws-well-architected-reviewFrom the publisher
This workflow performs a structured AWS Well-Architected Framework (WAF) review against your workload's IaC files and deployed infrastructure. It identifies risks across all 6 WAF pillars and creates GitHub issues to track remediation.
Fetch current AWS WAF best practices:
https://docs.aws.amazon.com/wellarchitected/latest/framework/welcome.htmlScan the repository for IaC files:
**/*.tf**/*.yaml, **/*.json (CFn templates)lib/**/*.ts, bin/**/*.ts, cdk.jsonIdentify key AWS services in use (compute, data, networking, security, observability) and generate a Mermaid architecture diagram.
* actions without justification)enforceSSL: true)aws guardduty list-detectors)arm64, EC2 Graviton)arm64 architecture adopted (20% cost reduction)For each finding, classify:
ποΈ AWS Well-Architected Review Summary
π Review Results:
β’ IaC Files Analyzed: X
β’ AWS Services Identified: Y
β’ Total Findings: Z
β’ High Risk: A (immediate action required)
β’ Medium Risk: B (should address soon)
β’ Low Risk: C (nice to have)
π΄ Top High Risk Findings:
1. [Pillar]: [Finding] β [Why it matters]
2. [Pillar]: [Finding] β [Why it matters]
π‘ This will create Z individual GitHub issues + 1 EPIC issue.
β Proceed with creating GitHub issues? (y/n)
Label with "well-architected" and the pillar name (e.g., "security", "reliability").
Title: [WAF-<PILLAR>] [Brief Finding] β [Risk Level]
Body:
## ποΈ Well-Architected Finding: [Brief Title]
**Pillar**: [Name] | **Risk Level**: [High/Medium/Low] | **Effort**: [Low/Medium/High]
### π Description
[Clear explanation of the finding and why it matters]
### π§ Remediation
**IaC Fix** (preferred):
```hcl
# Terraform example
resource "aws_s3_bucket_server_side_encryption_configuration" "example" {
bucket = aws_s3_bucket.example.id
rule {
apply_server_side_encryption_by_default {
sse_algorithm = "aws:kms"
}
}
}
```
**AWS CLI fallback**:
```bash
aws s3api put-bucket-encryption --bucket <name> \
--server-side-encryption-configuration '{"Rules":[{"ApplyServerSideEncryptionByDefault":{"SSEAlgorithm":"aws:kms"}}]}'
```
### π AWS Reference
- [WAF Best Practice Link]
- [AWS Documentation Link]
### β
Validation
- [ ] Change implemented in IaC and deployed
- [ ] AWS Config rule passes (if applicable)
- [ ] Security Hub finding resolved (if applicable)
**Well-Architected Question**: [WAF question this maps to]
Label with "well-architected" and "epic".
Title: [EPIC] AWS Well-Architected Review β X findings across 6 pillars
Body: Executive summary with pillar breakdown table (finding counts by pillar and risk level), Mermaid architecture diagram, prioritized checklist linking all individual issues (High β Medium β Low), and success criteria:
Β© 2026 Skills Rack.
---name: aws-well-architected-reviewdescription: Perform an AWS Well-Architected Framework review of the current workload IaC and architecture, generatingβ¦---# skills/aws-well-architected-review/SKILL.mdFAQ
Download skills/aws-well-architected-review/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/github/awesome-copilot.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.