CtrlK
BlogDocsLog inGet started
Tessl Logo

resilience-program-design

Designs a resilience program: how to structure and standardize resilience policies across an organization, team, or portfolio (tiered policy model with availability/RTO/RPO targets and DR approach selection), and how often to run resilience activities (operational cadence). Applies when the user asks how to structure policies org-wide, what tiers/targets to set, which DR approach fits a tier, or how frequently to run assessments, FIS experiments, GameDays, or autoshift practice. Does not apply to creating or configuring a specific policy or resource for a single workload (use resilience-hub-getting-started), to step-by-step lifecycle execution (see aws-resilience-lifecycle), or to service-specific setup.

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

Well-structured, actionable planning guidance that avoids concept padding and uses concrete enum values, cadences, and IAM controls. The main weakness is mild verbosity from repeated verification hedges and enum-value caveats.

Suggestions

Consolidate the repeated 'verify the valid values from the API/docs' disclaimers into a single stated convention near the top of the Structuring policies section to cut repeated tokens.

Tighten the 'illustratively — resolve the actual enum values against the API before recommending' hedges into one sentence so the example reads as guidance rather than caveat.

Consider an explicit mini-checklist for the tier-targets recommendation (e.g. 'For each tier: pick SLO, set RTO/RPO, choose DR approach, check for contradictions') to make the workflow sequence and its validation step more explicit.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence (no concept padding like 'what is RTO'), but the repeated 'verify via API/docs' disclaimers and 'illustratively — resolve the actual enum values' hedges add tokens that could be tightened.

4 / 5

Actionability

Concrete and specific: named DR-approach enum values, SLO values, RTO ranges, cadence frequencies, specific IAM condition keys, and a worked tier-to-targets example; minor gaps because enum values are explicitly left unverified against the API.

4 / 5

Workflow Clarity

Clear conceptual sequence (classify criticality -> set tier targets -> match DR -> cadence -> security) with checkpoints ('confirm valid values from API/docs', 'Warn against contradictory policies'); not a destructive-execution workflow so the batch cap does not bind, but checkpoints are advisory rather than explicit feedback loops.

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files, organized into clear headed sections (Overview, Structuring policies, Cadence, Security); the simple-skill exception applies and external links are limited to further-reading references.

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.

A strong description: third-person voice, concrete capabilities, natural trigger phrases, and explicit what/when coverage with a disambiguating boundary clause. No meaningful gaps to address.

DimensionReasoningScore

Specificity

Names multiple concrete actions ('structure and standardize resilience policies', 'availability/RTO/RPO targets and DR approach selection', 'run resilience activities (operational cadence)') with comprehensive coverage of the program-design domain.

5 / 5

Completeness

Clearly answers both 'what' ('Designs a resilience program...') and 'when' ('Applies when the user asks...') with concrete trigger phrases, plus an explicit negative-boundary clause.

5 / 5

Trigger Term Quality

Includes the natural phrases a user would actually say: 'how to structure policies org-wide', 'what tiers/targets to set', 'which DR approach fits a tier', 'how frequently to run assessments, FIS experiments, GameDays, or autoshift practice'.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (program-level design) and explicitly disambiguates sibling skills ('use resilience-hub-getting-started', 'see aws-resilience-lifecycle'), minimizing conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.