resilience-hub-getting-started

Sets up AWS Resilience Hub v2 from scratch: creates resilience policies with SLO targets, registers systems and user journeys, onboards services with input sources, and runs a first failure mode assessment. Applies when the user wants to get started with Resilience Hub v2, create a policy, onboard a service, or run an assessment — including creating one concrete policy with specific availability/RTO/RPO targets and a DR approach for a single service (even a tier-1 one). Does not apply to FIS experiments or ARC routing controls.

Quality

92%

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

92%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 skill body: lean overview with appropriate delegation to a detailed, validated procedure, plus genuinely useful troubleshooting and security sections. The main improvement would be slightly more executable specificity in the troubleshooting section.

Dimension	Reasoning	Score
Conciseness	A lean ~45-line body with no explanation of concepts Claude already knows; every section carries non-obvious signal such as the MCP-vs-local file guardrail and the 'three s's' policy-spelling note.	5 / 5
Actionability	Concrete commands appear in troubleshooting ('aws resiliencehubv2 list-failure-mode-assessments') and security (SSE-KMS, aws:SecureTransport, aws:SourceAccount), but the main setup steps are delegated to the reference and some troubleshooting guidance ('Verify input sources are correct') stays high-level.	4 / 5
Workflow Clarity	The body directs the reader to 'follow the procedure exactly', and the referenced procedure sequences steps 1-10 with explicit validation checkpoints and feedback loops: verify dependencies before any API call, poll until SUCCESS/FAILED, MUST NOT proceed until complete, and retry on the invoker-role error.	5 / 5
Progressive Disclosure	The body is a concise overview pointing to a single, clearly signaled, one-level-deep reference (references/setup-procedure.md, verified to exist with no nested references), keeping the SKILL.md itself minimal.	5 / 5
	Total	19 / 20 Passed

Description

92%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 description: third-person, concrete, and comprehensive, with an explicit trigger clause and a clear negative boundary. The only weakness is modest synonym coverage in the trigger terms.

Dimension	Reasoning	Score
Specificity	Lists four concrete, comprehensive actions — 'creates resilience policies with SLO targets, registers systems and user journeys, onboards services with input sources, and runs a first failure mode assessment' — with specific artifacts named for each.	5 / 5
Completeness	Explicitly answers both what (four concrete setup actions) and when ('Applies when the user wants to get started with Resilience Hub v2, create a policy, onboard a service, or run an assessment'), with concrete trigger phrases and a negative boundary for FIS/ARC.	5 / 5
Trigger Term Quality	'get started with Resilience Hub v2, create a policy, onboard a service, or run an assessment' are natural user phrases, but common synonyms such as 'disaster recovery', 'configure', or 'resilience policy' are absent from the trigger clause.	4 / 5
Distinctiveness Conflict Risk	Clear niche (first-time AWS Resilience Hub v2 setup) with explicitly excluded adjacent domains ('Does not apply to FIS experiments or ARC routing controls'), minimizing wrong-skill triggering.	5 / 5
	Total	19 / 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/resilience-hub-getting-started/SKILL.md
Commit: b8171ad

Reviewed: 5 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.