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

78%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/specialized-skills/resilience-skills/recovery-controller-setup/SKILL.md

Quality

Content

57%

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

Well-structured overview with excellent progressive disclosure and disciplined scope guardrails, but the body itself is mostly navigation — the executable, sequenced procedure with validation lives in the reference rather than the SKILL.md body, capping actionability and workflow clarity.

Suggestions

De-duplicate the scope statement between the CRITICAL CONSTRAINT section and the Overview to tighten conciseness.

Inline a minimal concrete command or two (e.g. the cluster/control-panel creation or a zonal-shift call) so the body is actionable without forcing a reference read for the first step.

Surface at least one validation checkpoint inline (e.g. verifying a routing-control state or confirming zonal-shift resource support) to raise workflow clarity for these production-traffic-affecting operations.

Dimension	Reasoning	Score
Conciseness	The body is operational and free of concept-explainer padding, but the CRITICAL CONSTRAINT scope statement is repeated in the Overview ('Domain expertise for configuring ARC routing controls, safety rules, zonal shift, and zonal autoshift') and the full redirect blockquote could be tightened; not quite the lean level-3 anchor.	2 / 3
Actionability	Navigation is concrete (specific file paths, MCP 'file=' parameters, per-section descriptions), but the body contains no executable code or commands itself — the actual CLI steps are deferred to references/arc-procedures.md, matching 'some concrete guidance but incomplete'.	2 / 3
Workflow Clarity	The section order is present (constraint → load-method guardrail → configure → troubleshooting → security) but the sequenced multi-step procedure with validation checkpoints lives in the reference, not the body; for traffic-shifting (risky) operations, absent in-body validation caps this at 2.	2 / 3
Progressive Disclosure	Clear overview body pointing to two real one-level-deep references ([references/arc-procedures.md], [references/security-considerations.md]) with well-signaled links and per-file content descriptions, matching the clean one-level-deep anchor.	3 / 3
	Total	9 / 12 Passed

Description

100%

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 description: concrete actions, natural triggers, explicit what/when guidance, and clear boundary-setting against adjacent skills. No first/second-person voice, no vague fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions in third person ('Configures AWS Application Recovery Controller (ARC)', 'routing controls with safety rules for cross-Region failover', 'zonal shift / zonal autoshift for AZ-impairment recovery', 'shifting traffic out of a specific Availability Zone (AZ) for an ALB/NLB'), matching the 'lists multiple specific concrete actions' anchor rather than the partial level 2.	3 / 3
Completeness	Explicitly states both what it does ('Configures ARC... routing controls... zonal shift / zonal autoshift') and when to use it ('Applies when setting up failover routing, configuring safety rules, enabling zonal shift... Also applies when shifting traffic out of a specific Availability Zone'), satisfying the explicit what-and-when anchor.	3 / 3
Trigger Term Quality	Covers natural user phrasing — 'setting up failover routing', 'configuring safety rules', 'enabling zonal shift', 'configuring zonal autoshift with practice runs', 'shifting traffic out of a specific Availability Zone (AZ)' — giving good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Narrow ARC niche with explicit carve-outs ('For a broader... question, see aws-resilience-lifecycle', 'Does not apply to Resilience Hub setup or FIS experiments'), making it unlikely to trigger for the wrong skill.	3 / 3
	Total	12 / 12 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: 222ce56

Reviewed: 3 days 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.