aws-waf-reliability-review
Review AWS workload reliability posture against the Well-Architected Framework Reliability Pillar. Covers service quotas, workload architecture, change management, backup and DR strategy, and failure isolation. Use when auditing availability design, planning disaster recovery, or
Install
npx skills add https://github.com/VincentChuWaiChow/vanguard-frontier-agentic/tree/master/skills/aws/aws-waf-reliability-review
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install vincentchuwaichow-vanguard-frontier-agentic@llmmart
git clone https://github.com/VincentChuWaiChow/vanguard-frontier-agentic.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole vincentchuwaichow/vanguard-frontier-agentic collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
AWS WAF Reliability Pillar Review
Purpose
Act as the AWS WAF Reliability Pillar reviewer — assess workload resilience against the five reliability design principles and produce actionable recommendations for improving availability, recovery, and change safety.
When to use
- Preparing for a formal AWS Well-Architected Review (Reliability Pillar)
- Reviewing multi-AZ or multi-region architecture, Auto Scaling, DR strategy, or backup posture
- Evaluating SLO targets, error budgets, or chaos engineering practices
Lean operating rules
- Always confirm SLO/RTO/RPO targets before assessing architecture gaps.
- Prefer
AwsDocumentationMcpServerwhen available. Otherwise fall back to official docs. - Separate confirmed facts from inference. If state was not queried, say so.
- Challenge single-AZ deployments, untested recovery, missing DLQs, and assumed capacity headroom.
- Load references only when needed; do not pull all deep guidance into short answers.
References
Load these only when needed:
- Workflow and output contract — use when executing the full WAF reliability review, formatting findings, or generating the final assessment report.
- Safety checklist — use before recommending any Auto Scaling policy, backup, DR, or production-impacting change.
- Official sources — use when grounding AWS service reliability behavior or citing WAF documentation.
- Well-Architected Reliability Review Guide — use for domain-specific failure modes, safe workflow, verification targets, and pushback criteria.
Files (vanguard-frontier-agentic)
-
references
-
official-sources.md 2 KB
Loading… -
safety-checklist.md 1.2 KB
Loading… -
well-architected-reliability-review.md 3.1 KB
Loading… -
workflow-and-output.md 1.9 KB
Loading…
-
-
metadata.json 1.1 KB
Loading… -
SKILL.md 2.2 KB
--- name: aws-waf-reliability-review description: "Review AWS workload reliability posture against the Well-Architected Framework Reliability Pillar. Covers service quotas, workload architecture, change management, backup and DR strategy, and failure isolation. Use when auditing availability design, planning disaster recovery, or preparing for a formal WAF Reliability Pillar review." allowed-tools: Read Grep Glob metadata: author: "github: VincentChuWaiChow" version: "0.1.4" updated: "2026-06-02" category: resilience --- # AWS WAF Reliability Pillar Review ## Purpose Act as the AWS WAF Reliability Pillar reviewer — assess workload resilience against the five reliability design principles and produce actionable recommendations for improving availability, recovery, and change safety. ## When to use - Preparing for a formal AWS Well-Architected Review (Reliability Pillar) - Reviewing multi-AZ or multi-region architecture, Auto Scaling, DR strategy, or backup posture - Evaluating SLO targets, error budgets, or chaos engineering practices ## Lean operating rules - Always confirm SLO/RTO/RPO targets before assessing architecture gaps. - Prefer `AwsDocumentationMcpServer` when available. Otherwise fall back to official docs. - Separate confirmed facts from inference. If state was not queried, say so. - Challenge single-AZ deployments, untested recovery, missing DLQs, and assumed capacity headroom. - Load references only when needed; do not pull all deep guidance into short answers. ## References Load these only when needed: - [Workflow and output contract](references/workflow-and-output.md) — use when executing the full WAF reliability review, formatting findings, or generating the final assessment report. - [Safety checklist](references/safety-checklist.md) — use before recommending any Auto Scaling policy, backup, DR, or production-impacting change. - [Official sources](references/official-sources.md) — use when grounding AWS service reliability behavior or citing WAF documentation. - [Well-Architected Reliability Review Guide](references/well-architected-reliability-review.md) — use for domain-specific failure modes, safe workflow, verification targets, and pushback criteria.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.