recovery-controller-setup

Configures AWS Application Recovery Controller (ARC) for operational resilience: routing controls with safety rules for cross-Region failover, and zonal shift / zonal autoshift for AZ-impairment recovery. Applies when setting up failover routing, configuring safety rules, enabling zonal shift, or configuring zonal autoshift with practice runs. Also applies when shifting traffic out of a specific Availability Zone (AZ) for an ALB/NLB or other resource. For a broader "an AZ is impaired, what is my response across services" question, see aws-resilience-lifecycle. Does not apply to Resilience Hub setup or FIS experiments.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured overview that uses progressive disclosure effectively and provides concrete inline directives, but it lacks visible validation checkpoints for the destructive failover operations it governs, which caps workflow clarity. Some restatement in the constraint section could be tightened.

Suggestions

Add an explicit validation/verification checkpoint in the body for destructive operations (e.g., confirm routing-control state propagated to traffic before declaring failover complete, or verify zonal-shift status after enabling) so workflow clarity is not capped at 3.

Tighten the CRITICAL CONSTRAINT section by stating the two-capability scope once and referencing it, rather than restating the routing-control/zonal-shift framing multiple times and inlining the full redirect quote template.

Surface one or two key executable commands inline (e.g., the CLI to check a routing-control state or zonal-shift status) so the body is self-sufficient for the most common action without requiring a jump to the reference.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining concepts Claude already knows (no 'what is ARC/AZ' padding), but the CRITICAL CONSTRAINT section restates the two-capability framing several times and includes a full redirect quote template that could be trimmed.	4 / 5
Actionability	Inline guidance is concrete and specific — exact reference paths, the exact redirect wording to use, and precise MCP file-fetch syntax (file="references/arc-procedures.md") — with the detailed procedure appropriately delegated to the reference file.	4 / 5
Workflow Clarity	The body gives a clear gate-then-redirect-then-follow-procedure sequence with a strong scope guardrail, but it surfaces no validation/verification checkpoints for the destructive failover and zonal-shift operations; per the destructive-operations cap this cannot exceed 3.	3 / 5
Progressive Disclosure	The body is a clear overview with well-signaled, one-level-deep references to arc-procedures.md and security-considerations.md (both present in references/), each described by what it contains; navigation is easy and content is appropriately split.	5 / 5
	Total	16 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states what the skill configures and when to use it, with concrete trigger terms and explicit boundary guidance against adjacent skills. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Names the domain (ARC) and multiple concrete capabilities — 'routing controls with safety rules for cross-Region failover' and 'zonal shift / zonal autoshift for AZ-impairment recovery' — giving comprehensive coverage of what it configures.	5 / 5
Completeness	Explicitly answers both 'what' (configures ARC routing controls and zonal shift) and 'when' ('Applies when setting up failover routing... Also applies when shifting traffic...'), with concrete trigger phrases and explicit non-applicability boundaries.	5 / 5
Trigger Term Quality	Includes natural phrases users would say — 'setting up failover routing', 'configuring safety rules', 'enabling zonal shift', 'shifting traffic out of a specific Availability Zone (AZ) for an ALB/NLB' — with synonyms (ALB/NLB, AZ) covered.	5 / 5
Distinctiveness Conflict Risk	Clear niche with explicit redirects ('see aws-resilience-lifecycle') and exclusions ('Does not apply to Resilience Hub setup or FIS experiments'), minimizing conflict risk with adjacent skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: aws/agent-toolkit-for-aws
Path: skills/specialized-skills/resilience-skills/recovery-controller-setup/SKILL.md
Commit: d6ad2e4

Reviewed: about 2 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.