setting-up-cloudwatch-alarm-notifications

Sets up notification channels for CloudWatch alarms using SNS topics and subscriptions. Always use this skill when configuring alarm notifications — it creates encrypted SNS topics, configures topic policies for CloudWatch access, sets up email/SMS/webhook subscriptions, and links alarms to notification actions with proper security 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.

The body is lean and well-structured with a clearly signaled one-level-deep reference and concrete troubleshooting commands, but it delegates the entire primary setup procedure to the reference without inline steps or validation checkpoints, leaving the main workflow as just a pointer.

Suggestions

Inline a concise numbered summary of the core setup steps in the 'Set up alarm notifications' section (create encrypted SNS topic → attach topic policy → add email/SMS/webhook subscriptions → link the alarm's AlarmActions to the topic ARN) so the primary workflow is actionable without opening the reference.

Add an explicit validation checkpoint after setup — e.g., publish a test message to the topic and confirm subscription delivery, or run `aws cloudwatch describe-alarms` to verify AlarmActions and ActionsEnabled=true — before declaring the alarm notifications complete.

Trim the redundancy between the Overview and the frontmatter description (the Overview restates the same capability list), keeping the Overview to a one-line orienting summary to better respect the token budget.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude's competence (no explanations of what CloudWatch/SNS are), and defers detail to the reference; the only mild redundancy is the Overview restating the description's capability list, which is not enough to drop it below the lean/efficient anchor.	3 / 3
Actionability	Troubleshooting provides concrete executable commands (e.g., `aws sns list-subscriptions-by-topic`, checking for "Confirmed", E.164 example, `aws cloudwatch describe-alarms`), but the primary setup section offers only "follow the procedure exactly. See [reference]" — a pointer rather than concrete actions, leaving the main task incomplete in the body.	2 / 3
Workflow Clarity	The multi-step setup (create topic, attach policy, add subscriptions, link alarm) is delegated entirely to the reference with no inline sequence, and verification appears only in troubleshooting rather than as explicit checkpoints in the primary workflow.	2 / 3
Progressive Disclosure	Clear Overview, a well-signaled one-level-deep reference (the link path matches the actual `references/setup-cloudwatch-alarm-notifications.md` file), and organized Troubleshooting subsections — content is appropriately split with easy navigation.	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.

The description is strong: it enumerates multiple concrete actions, provides natural trigger terms, and explicitly covers both what the skill does and when to use it via a clear "Always use this skill when..." trigger. Voice is third-person and the niche is distinct, minimizing conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — "creates encrypted SNS topics", "configures topic policies for CloudWatch access", "sets up email/SMS/webhook subscriptions", and "links alarms to notification actions" — in proper third-person voice, matching the anchor for comprehensive concrete actions.	3 / 3
Completeness	Explicitly answers both what (the four concrete actions) and when ("Always use this skill when configuring alarm notifications"), which is an explicit trigger clause equivalent to a "Use when..." statement, so it is not capped at 2.	3 / 3
Trigger Term Quality	Includes natural terms a user would actually say — "CloudWatch alarms", "alarm notifications", "notification channels", and "SNS topics and subscriptions" — giving good coverage rather than a single keyword.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche — CloudWatch alarm notification setup via SNS — with distinct triggers unlikely to fire for unrelated skills.	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/operations-skills/setting-up-cloudwatch-alarm-notifications/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.