sns
AWS SNS notification service for pub/sub messaging. Use when creating topics, managing subscriptions, configuring message filtering, sending notifications, or setting up mobile push.
86
82%
Does it follow best practices?
Impact
94%
0.97xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
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.
This is a well-crafted skill description that follows best practices. It uses third person voice, clearly identifies the AWS SNS domain, lists specific capabilities, and includes an explicit 'Use when...' clause with natural trigger terms. The description is concise yet comprehensive enough to distinguish it from other AWS or messaging-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'creating topics, managing subscriptions, configuring message filtering, sending notifications, setting up mobile push' - these are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('AWS SNS notification service for pub/sub messaging') and when ('Use when creating topics, managing subscriptions, configuring message filtering, sending notifications, or setting up mobile push') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'SNS', 'topics', 'subscriptions', 'notifications', 'mobile push', 'pub/sub messaging', 'message filtering' - good coverage of terms someone working with AWS messaging would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to AWS SNS with distinct triggers like 'SNS', 'topics', 'subscriptions', 'mobile push' - unlikely to conflict with other AWS services or generic messaging skills due to the specific terminology. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable AWS SNS skill with excellent code examples in both CLI and Python. The main weaknesses are verbosity in the Core Concepts section (explaining things Claude knows), lack of validation checkpoints in workflows, and a monolithic structure that could benefit from splitting reference material into separate files.
Suggestions
Remove or significantly trim the Core Concepts section - Claude understands pub/sub, topics, and subscription protocols without explanation
Add validation steps to workflows, e.g., 'Verify subscription status before publishing' with code to check SubscriptionArn is not 'pending confirmation'
Split CLI Reference tables and detailed filter policy examples into separate reference files, keeping only essential patterns in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary explanations like the Core Concepts section explaining what topics are ('Named channels for publishing messages') and basic protocol descriptions that Claude already knows. | 2 / 3 |
Actionability | Excellent executable code examples throughout - both AWS CLI and boto3 Python code are copy-paste ready with realistic ARNs, complete imports, and proper syntax. Filter policy examples are concrete JSON that can be used directly. | 3 / 3 |
Workflow Clarity | The troubleshooting section provides good diagnostic steps, but the main patterns lack explicit validation checkpoints. For example, the fan-out pattern doesn't verify subscriptions were created successfully before publishing, and there's no guidance on confirming message delivery. | 2 / 3 |
Progressive Disclosure | The document has a clear table of contents and logical sections, but it's a monolithic 300+ line file. The CLI Reference tables and extensive filter policy examples could be split into separate reference files, with the main skill focusing on quick-start patterns. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- itsmostafa/aws-agent-skills
- Commit
5df6da7
- 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.