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

73%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/specialized-skills/resilience-skills/resilience-hub-multi-account/SKILL.md

Quality

Content

67%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.

The skill body is well-structured with a strong decision rule, executable command examples, and a clean one-level reference to a thorough SOP. Its main weakness is conciseness — the delegated-administrator/non-CLI-operation caveat is restated several times across sections.

Suggestions

Consolidate the repeated "no register-delegated-administrator CLI operation / Organizations integration is separate" caveat into one clearly marked section and reference it from the others to cut repetition.

Tighten the Overview by deferring the full Organizations-integration explanation to the Troubleshooting "Looking for a delegated-administrator setup" section, which already covers it.

Consider moving the inline `create-service` command duplication (present in both SKILL.md and the SOP) into a single shared block referenced once.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient but includes noticeable repetition — the same "there is no register-delegated-administrator CLI operation" point and the Organizations-vs-per-service distinction are restated in the Overview, the decision rule, the cross-account section, and Troubleshooting, which pads the token budget beyond what a leaner version would need.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands (the `create-service --permission-model` form with full JSON) and points to an executable SOP with explicit CLI commands, satisfying the mostly-executable-with-minor-gaps anchor; the only gap is that the bulk of executable steps live one level deep in the reference rather than inline.	4 / 5
Workflow Clarity	There is a clear decision rule framing two paths, a pointed "Configure multi-account setup → follow the procedure exactly" step, and the referenced SOP contains an explicit 5-step sequence with verification (`list-services`, `list-input-sources`) plus troubleshooting; minor checkpoints (e.g. a pre-flight validation callout) live in the reference rather than the body, keeping it just below the explicit-validation-steps anchor.	4 / 5
Progressive Disclosure	SKILL.md serves as a well-signaled overview with a single one-level-deep reference (references/multi-account-procedure.md, verified to exist) and clear navigation, matching the good-structure-mostly-clear anchor; the reference is real and appropriately scoped rather than nested.	4 / 5
	Total	15 / 20 Passed

Description

80%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.

The description is specific, explicitly answers both what and when with a clear trigger clause, and is well-differentiated from neighboring skills. Its main weakness is trigger-term naturalness, leaning on technical jargon over user-spoken phrases.

Suggestions

Add natural-sounding trigger phrases users actually say, e.g. "Use when the user asks to assess workloads across multiple accounts" or synonyms like "resilience/DR assessment across accounts".

Consider including the CLI namespace cue ("aws resiliencehubv2") only if it aids disambiguation; otherwise keep the description focused on user-facing outcomes.

Dimension	Reasoning	Score
Specificity	The description lists several concrete actions — "Configures AWS Resilience Hub v2", "Covers the per-service cross-account permission model", "cross-account IAM roles", and "centralized assessment from a single account" — which match the several-specific-actions-with-minor-gaps anchor better than the single-pair anchor at 3.	4 / 5
Completeness	It clearly answers 'what' (configures Resilience Hub v2 for multi-account resilience management, covering the permission model, cross-account IAM roles, centralized assessment) and explicitly answers 'when' with "Applies when the user wants to set up org-wide resilience or assess workloads that span multiple AWS accounts," matching the explicit-what-and-when-with-trigger-phrases anchor.	5 / 5
Trigger Term Quality	It surfaces relevant terms ("multi-account", "cross-account", "resilience management", "AWS Organization") but relies on fairly technical jargon and omits common natural variations a user might say (e.g. "resilience assessment", "DR assessment", "assess workloads across accounts"), so it sits at the some-relevant-keywords anchor rather than the comprehensive anchor.	3 / 5
Distinctiveness Conflict Risk	The skill carves a clear niche (multi-account Resilience Hub v2 cross-account permission model) with distinct triggers that would not fire for generic IAM or single-account resilience skills, matching the clear-niche-minimal-conflict anchor.	5 / 5
	Total	17 / 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-multi-account/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.