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

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%

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

A well-organized overview that delegates the detailed procedure to a single real reference and keeps concise, concrete troubleshooting and security guidance inline. The main weakness is that the body's core setup section and workflow checkpoints live entirely in the reference rather than being surfaced in the body.

Suggestions

Add a brief inline step list or checklist in the 'Set up Resilience Hub v2' section (e.g. policy → system → journey → service → input sources → assessment) so the workflow sequence and key validation/polling checkpoints are visible without opening the reference.

Surface one or two of the most critical executable commands from setup-procedure.md inline (such as the create-policy and start-failure-mode-assessment invocations) to raise actionability for the core task.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it does not explain what Resilience Hub is or restate basic concepts, and the MCP-vs-local guardrail conveys non-obvious operational detail that earns its tokens.	3 / 3
Actionability	Troubleshooting and Security sections give concrete, executable specifics (e.g. `aws resiliencehubv2 list-failure-mode-assessments`, `aws:SecureTransport`, `AWSResilienceHubAsssessmentExecutionPolicy`), but the core setup task is delegated as a pointer to the reference rather than carrying inline executable commands, so it is not fully copy-paste ready at level 3.	2 / 3
Workflow Clarity	The multi-step setup workflow is cleanly delegated to setup-procedure.md, but the body itself does not surface the sequence or its validation/polling checkpoints; only the troubleshooting addenda offer implicit error-recovery guidance, leaving it at level 2 rather than 3.	2 / 3
Progressive Disclosure	A concise overview with a single well-signaled, one-level-deep reference (references/setup-procedure.md, confirmed to exist) and inline-only addenda for troubleshooting/security — the clean split matches the level-3 anchor.	3 / 3
	Total	10 / 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, third-person description that names concrete actions, gives explicit trigger conditions, and draws a clear negative boundary. It concisely conveys both capability and applicability without padding.

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" — matching the multi-action anchor rather than the single-action level 2.	3 / 3
Completeness	Explicitly answers both what (the setup actions) and when via an "Applies when the user wants to get started..." clause, plus a concrete-deliverable qualifier and a negative boundary, satisfying the level-3 anchor.	3 / 3
Trigger Term Quality	Covers natural phrasings a user would actually say ("get started with Resilience Hub v2", "create a policy", "onboard a service", "run an assessment") with good variation, not just jargon.	3 / 3
Distinctiveness Conflict Risk	Narrowly scoped to Resilience Hub v2 setup with an explicit "Does not apply to FIS experiments or ARC routing controls" boundary, making conflicts with adjacent skills unlikely.	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/resilience-hub-getting-started/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.