aws-resilience-lifecycle

Guides the end-to-end AWS resilience lifecycle integrating Resilience Hub v2, Fault Injection Service, and Application Recovery Controller. Covers the Define → Test → Operate workflow: from policy creation through failure mode assessment, to FIS experiment validation, to ARC operational controls. Applicable when the user wants a complete resilience strategy, needs to connect findings to experiments to controls, or is planning a resilience program. Also applicable for the meta question of whether marking NGRH findings as resolved is enough, whether they are "done" after resolving findings, or how to validate findings before resolving them. Not applicable for resolving or remediating a specific individual finding (see resilience-hub-failure-mode-assessment), or when a single service is explicitly named (e.g. "what FIS experiment should I run").

Quality

89%

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

78%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 coordination skill: it stays in its lane, delegates command detail to references, and bakes a critical validation requirement into the workflow. Main weakness is mild repetition in the findings-validation messaging.

Suggestions

Consolidate the 'paper compliance' message so it appears once (e.g. in the Validate findings section) and is referenced rather than restated in Troubleshooting.

Inline a short numbered Define→Test→Operate checklist in SKILL.md so the core workflow is visible without opening lifecycle-workflow.md.

Add one concrete example CLI invocation (e.g. a minimal resiliencehubv2 assessment command) inline so the most common entry point is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Lean body that assumes Claude's competence (no basics about FIS/ARC explained) and earns most of its tokens, but the 'Validate findings' and 'Findings resolved' sections restate the paper-compliance point several times and could be tightened.	4 / 5
Actionability	Concrete procedural guidance ('create a policy, register your service, run an assessment'; 'Run the experiment, confirm the system recovers... then mark resolved') with executable commands delegated to api-reference.md one hop away — appropriate for an instruction skill, with minor gaps.	4 / 5
Workflow Clarity	The Define→Test→Operate sequence is clear with an explicit validation checkpoint ('MUST validate each remediation... BEFORE marking the finding resolved') and a troubleshooting feedback loop; the detailed step sequence and checklist live in lifecycle-workflow.md rather than inline, leaving a minor gap.	4 / 5
Progressive Disclosure	Clear overview body pointing one level deep to three real, well-signaled reference files (lifecycle-workflow.md, best-practices.md, api-reference.md), with a guardrail explaining how to load them under MCP vs local install — exemplary content split and navigation.	5 / 5
	Total	17 / 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.

An exemplar description: third-person voice, concrete capabilities, explicit positive and negative triggers, and clear disambiguation from sibling skills. It tells Claude exactly when to load this skill versus a narrower one.

Dimension	Reasoning	Score
Specificity	Names three concrete services (Resilience Hub v2, FIS, ARC) and multiple specific actions — 'policy creation', 'failure mode assessment', 'FIS experiment validation', 'ARC operational controls' — giving comprehensive coverage of the lifecycle.	5 / 5
Completeness	Explicitly answers both 'what' (integrates three services across Define→Test→Operate) and 'when' ('Applicable when... ', 'Also applicable for...', 'Not applicable for...'), with concrete positive and negative trigger phrases.	5 / 5
Trigger Term Quality	Covers natural phrases a user would say — 'complete resilience strategy', 'planning a resilience program', 'marking NGRH findings as resolved', 'validate findings' — including synonyms (NGRH findings, findings, resolve findings) and meta-question variants.	5 / 5
Distinctiveness Conflict Risk	Clear niche (integrated three-service resilience lifecycle) with explicit negative boundaries steering away from sibling skills ('Not applicable for resolving... a specific individual finding (see resilience-hub-failure-mode-assessment), or when a single service is explicitly named').	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/aws-resilience-lifecycle/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.