agentleFS
Sign inStart free
ulises-jeremiasulises-jeremias/agent-toolkit/skills/cloud/aws-well-architected-review/SKILL.md

aws-well-architected-review

Skill19 starsChanged 2 months agoMITView on GitHub

WHAT — AWS Well-Architected Framework review (6 pillars) — operational excellence, security, reliability, performance, cost, sustainability + WAR process. Checklist for workload evaluation on AWS; complementary to official AWS MCP for live account data.

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Must not exfiltrate credentials.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

AWS Well-Architected Review (WHAT)

Sources (2026-08-12): Framework https://docs.aws.amazon.com/wellarchitected/latest/framework/the-pillars-of-the-framework.html + https://docs.aws.amazon.com/wellarchitected/latest/framework/welcome.html + https://aws.amazon.com/architecture/well-architected/; WAR Tool https://docs.aws.amazon.com/wellarchitected/latest/userguide/getting-started.html; MCP awslabs/mcp https://github.com/awslabs/mcp + https://github.com/aws/mcp-proxy-for-aws GA https://aws.amazon.com/blogs/aws/the-aws-mcp-server-is-now-generally-available/; servers awslabs.core-mcp-server, awslabs.well-architected-security-mcp-server 0.1.3, awslabs.ecs-mcp-server 0.1.17 uvx awslabs.*@latest AWS_PROFILE/AWS_REGION.

Provider hierarchy: official MCP (awslabs/mcp family, mcp-proxy-for-aws GA) > custom prompts for account-aware ops (live context, auth via AWS_PROFILE/AWS_REGION); prompts (this skill checklist) remain fallback for offline/low-privilege/CI. See docs/cloud/research-384-candidates.md.

When to use

  • Designing or reviewing workload on AWS against 6 pillars.
  • Running Well-Architected Review (WAR) without console Tool access.

Instructions

  1. Run checklist per pillar: operational excellence (runbooks, observability), security (IAM, encryption, least privilege), reliability (multi-AZ, backup, retry), performance (right-sizing, caching), cost (graviton, S3 lifecycle), sustainability (right-sizing, serverless).
  2. Map to cloud-design-patterns where relevant (e.g., reliability → Circuit Breaker).
  3. If live account: delegate to awslabs/mcp (mcp-proxy-for-aws or awslabs.core-mcp-server uvx) for context; else do NOT paste ${AWS_*} secrets — use placeholders ${AWS_PROFILE}, ${AWS_REGION}, ${AWS_ACCOUNT_ID}.
  4. Record findings as High/Medium/Low risk per pillar and link to lenses/hands-on labs.

Security

  • Must not exfiltrate credentials; use ${AWS_*} placeholders; mark aws-well-architected-review as optional (no vendor lock).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free