resilience-hub-multi-account

Configures AWS Resilience Hub v2 for multi-account resilience management across an AWS Organization. Covers the per-service cross-account permission model, cross-account IAM roles, and centralized assessment from a single account. Applies when the user wants to set up org-wide resilience or assess workloads that span multiple AWS accounts.

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

85%

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

The body is highly actionable with executable commands and a clearly sequenced, validated workflow delegated to a well-structured one-level-deep reference. Its main weakness is conciseness: the delegated-administrator disambiguation and the loading-mode guardrail are repeated or padded.

Suggestions

Consolidate the 'no register-delegated-administrator CLI operation' clarification to a single authoritative location (e.g. the troubleshooting subsection) and briefly cross-reference it instead of restating it in the overview, decision rule, and body section.

Tighten the 'Guardrail — where this skill's own files live' section into a shorter MCP-vs-local dispatch rule; the current prose can be cut roughly in half without losing the instruction.

Trim the explanatory parentheticals in the Overview paragraph (e.g. the v1/v2 CLI namespace aside) and move deeper disambiguation into the reference where the procedure already covers it.

Dimension	Reasoning	Score
Conciseness	Assumes Claude's competence and avoids explaining basics, but the 'no register-delegated-administrator CLI operation' point is restated 3–4 times and the MCP-vs-local guardrail is lengthy, so it is mostly efficient with tightening room rather than fully lean.	2 / 3
Actionability	Provides a real, copy-paste-ready 'aws resiliencehubv2 create-service ... --permission-model' command with the complete JSON structure, plus concrete verification and troubleshooting guidance — fully executable rather than pseudocode.	3 / 3
Workflow Clarity	A clear decision rule (path 1 vs path 2) sequences the choice, and the delegated procedure defines Steps 1–5 with explicit validation checkpoints (Step 1 verify dependencies, Step 5 verify cross-account visibility) and error-recovery troubleshooting.	3 / 3
Progressive Disclosure	SKILL.md is an overview pointing to one clearly signaled, one-level-deep reference (references/multi-account-procedure.md, verified to exist) with content appropriately split; navigation is easy and no nested 2+ level chains.	3 / 3
	Total	11 / 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.

The description is specific, third-person, and clearly states both capabilities and explicit trigger conditions for a distinct niche. It is a strong example of the 'good_overall' pattern with an explicit 'Applies when' clause.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities — 'per-service cross-account permission model, cross-account IAM roles, and centralized assessment from a single account' — matching the multiple-specific-actions anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	Explicitly answers both what ('Configures AWS Resilience Hub v2 for multi-account resilience management...') and when ('Applies when the user wants to set up org-wide resilience or assess workloads that span multiple AWS accounts'), satisfying the 'Use when...' equivalent.	3 / 3
Trigger Term Quality	Captures natural user phrasings ('multi-account resilience management', 'set up org-wide resilience', 'assess workloads that span multiple AWS accounts') with good coverage; not reduced to 2 since common variations are present.	3 / 3
Distinctiveness Conflict Risk	Scoped to a narrow niche (AWS Resilience Hub v2 multi-account) with distinct triggers unlikely to collide with other skills; clearly above the 'could still overlap' anchor at 2.	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-multi-account/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.