sns-topic-config
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill sns-topic-configSns Topic Config - Auto-activating skill for AWS Skills. Triggers on: sns topic config, sns topic config Part of the AWS Skills skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, functioning more as a label than a useful skill description. It provides no information about what actions the skill performs (create, modify, delete, view topics?), no natural language triggers users would actually say, and no guidance on when Claude should select this skill over others.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates, configures, and manages AWS SNS topics including subscriptions, access policies, and delivery settings.'
Include a 'Use when...' clause with natural trigger terms like 'Use when the user needs to set up SNS topics, configure pub/sub messaging, manage notification subscriptions, or work with AWS Simple Notification Service.'
Add common variations of terminology users might use: 'SNS', 'Simple Notification Service', 'pub/sub', 'message topics', 'notification topics', 'AWS messaging'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - it only states it's an 'auto-activating skill for AWS Skills' without explaining what it actually does with SNS topic configuration. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming the topic, and the 'when' guidance is just a repetitive trigger phrase without meaningful context about use cases. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('sns topic config' listed twice) and overly technical. Missing natural variations users might say like 'SNS', 'notification service', 'topic settings', 'AWS notifications', or 'pub/sub'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'SNS topic config' is somewhat specific to a particular AWS service, the lack of detail about what operations it performs could cause confusion with other AWS-related skills or general configuration skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is an empty template that provides zero actionable information about SNS topic configuration. It consists entirely of placeholder text describing what a skill should do rather than actually teaching Claude how to configure SNS topics. The content fails on all dimensions as it contains no AWS-specific guidance, no code examples, and no concrete instructions.
Suggestions
Add concrete AWS CLI commands and CloudFormation/Terraform examples for creating and configuring SNS topics (e.g., `aws sns create-topic --name MyTopic`)
Include specific configuration patterns such as access policies, encryption settings, delivery policies, and subscription filters with executable code
Define a clear workflow for SNS topic setup: create topic -> configure access policy -> add subscriptions -> verify with test message
Add validation steps such as checking topic ARN, verifying IAM permissions, and testing message delivery to subscribed endpoints
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely boilerplate with no actual SNS topic configuration information. It explains what the skill does in abstract terms without providing any concrete guidance, wasting tokens on meta-description rather than actionable content. | 1 / 3 |
Actionability | No concrete code, commands, or specific instructions are provided. The content only describes what the skill claims to do ('provides step-by-step guidance') without actually providing any guidance, examples, or executable configurations. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for configuring SNS topics, no validation checkpoints, and no sequence of operations. The phrase 'step-by-step guidance' is mentioned but never delivered. | 1 / 3 |
Progressive Disclosure | The content is a flat template with no meaningful structure. There are no references to detailed documentation, no links to examples, and no organization of content by complexity or use case. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.