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 that stays concise, delegates the detailed procedure to one clearly-signaled reference, and still provides concrete troubleshooting and security guidance inline. The only soft spot is that the primary executable workflow lives entirely in the reference rather than the body.

Dimension	Reasoning	Score
Conciseness	The body is lean: it skips concepts Claude already knows, gives a brief overview, a necessary MCP-vs-local guardrail, and tight troubleshooting/security sections where every line is actionable.	5 / 5
Actionability	Troubleshooting and security sections contain concrete, executable detail (specific CLI calls, errorCode values, managed-policy ARNs, condition keys), but the core setup procedure is delegated to the reference rather than carried inline in the body.	4 / 5
Workflow Clarity	The referenced setup-procedure.md lays out a clearly sequenced 10-step workflow with explicit validation checkpoints (capture policyArn/systemArn/serviceArn, poll until SUCCESS/FAILED, MUST NOT proceed until complete, retry on invoker-role errors), so no validation-gap cap applies.	5 / 5
Progressive Disclosure	The body is a clean overview that points to a single, well-signaled one-level-deep reference (references/setup-procedure.md, which exists in the bundle) via a markdown link, with no nested reference chains.	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, third-person description that names concrete capabilities, gives explicit 'use when' triggers, and draws clear boundaries against neighbouring AWS resilience services. The only minor gap is that a few natural synonym triggers are implied rather than spelled out.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'creates resilience policies with SLO targets, registers systems and user journeys, onboards services with input sources, and runs a first failure mode assessment' — giving comprehensive coverage of the setup workflow rather than vague abstractions.	5 / 5
Completeness	Explicitly answers both 'what' (the setup actions) and 'when' ('Applies when the user wants to get started...'), and adds a concrete negative boundary ('Does not apply to FIS experiments or ARC routing controls').	5 / 5
Trigger Term Quality	Natural triggers like 'get started with Resilience Hub v2, create a policy, onboard a service, or run an assessment' map well to what a user would say, but a few natural variations (e.g. 'disaster recovery', 'SLO/RTO/RPO') are only implicit rather than stated as triggers.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (AWS Resilience Hub v2 first-time setup) with distinct triggers and an explicit exclusion clause, keeping conflict risk with adjacent AWS skills minimal.	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: d6ad2e4

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