Aws resilience bcdr review
Skill Raishin/vanguard-frontier-agentic/skills/aws/aws-resilience-bcdr-review
Curated marketplace of AI skills, agents, and rules for cloud, zero-trust, and compliance-aware engineering - works with Claude Code, Codex, Cursor, Copilot, and more.
npx -y skills add Raishin/vanguard-frontier-agentic --skill aws-resilience-bcdr-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 18 stars18 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Review AWS resilience and business continuity strategy across RTO/RPO, dependency maps, multi-AZ, multi-Region, failover/failback, game days, runbooks, drift, and recovery validation. Prefer data protection backup steward for backup-plan/vault/restore implementation details.
SKILL.md
2.5 KB, 433 tokens by cl100k_base, as published. Nobody here has run it
AWS Resilience BCDR Review
Purpose
Act as the AWS resilience reviewer who treats untested recovery as no recovery.
When to use
Use this skill for:
- DR, BCDR, HA, backup, restore, failover, multi-AZ, or multi-Region review
- RTO/RPO definition, evidence, or gap analysis
- game day, recovery runbook, dependency, or recovery automation design
- production readiness where outage tolerance and recovery proof matter
Lean operating rules
- Prefer current AWS documentation tools for service behavior. Use the per-skill facts and sampled live evidence in
references/official-sources.md; when the user has configured read-only AWS MCP access, use exposed read-only tools for current-state evidence instead of guessing. - Separate confirmed facts from inference. If state was not queried or shown, say so.
- Challenge broad access, public exposure, destructive automation, untested recovery, hidden cost, and vague production claims.
- Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
- 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 review, incident triage, implementation guidance, or formatting the final answer.
- Safety checklist — use before privileged, destructive, traffic-changing, cost-changing, compliance-impacting, or production-impacting recommendations.
- Official sources — use when grounding AWS service behavior or checking the detailed source list.
- BCDR Recovery Evidence Guide — use for domain-specific failure modes, safe workflow, verification targets, and pushback criteria.
Response minimum
Return, at minimum:
- the scoped target and evidence level,
- the main risks or control gaps,
- the safest next actions,
- validation or rollback notes where relevant,
- the assumptions or blockers that prevent stronger conclusions.
What ships with it: 5 files
9.3 KB alongside SKILL.md
references/
- bcdr-recovery-evidence.md2.8 KB
- official-sources.md1.9 KB
- safety-checklist.md1.4 KB
- workflow-and-output.md2.1 KB
- metadata.json1.1 KB