sqs-queue-setup
Sqs Queue Setup - Auto-activating skill for AWS Skills. Triggers on: sqs queue setup, sqs queue setup Part of the AWS Skills skill category.
35
3%
Does it follow best practices?
Impact
95%
1.04xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/13-aws-skills/sqs-queue-setup/SKILL.mdQuality
Discovery
7%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 description is extremely minimal, essentially just repeating the skill name without describing concrete capabilities, use cases, or trigger conditions. It fails to help Claude distinguish when to select this skill over other AWS-related skills. The description reads as auto-generated boilerplate rather than a thoughtfully crafted selection guide.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates and configures AWS SQS queues including standard and FIFO queues, dead-letter queues, access policies, and visibility timeout settings.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to create, configure, or manage SQS message queues, set up dead-letter queues, or configure queue policies in AWS.'
Remove the duplicate trigger term 'sqs queue setup' and replace with diverse natural language variations users might use, such as 'message queue', 'AWS messaging', 'queue permissions', 'FIFO queue'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'sqs queue setup' without describing any concrete actions like creating queues, configuring dead-letter queues, setting visibility timeouts, or defining access policies. It's essentially just a name repeated. | 1 / 3 |
Completeness | The 'what' is extremely weak (just 'sqs queue setup' with no elaboration on capabilities), and the 'when' is missing entirely — there is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms are 'sqs queue setup' repeated twice. Missing natural variations users would say like 'message queue', 'SQS', 'AWS queue', 'FIFO queue', 'dead letter queue', 'queue configuration', or 'messaging'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'SQS' does narrow it to a specific AWS service, which provides some distinctiveness. However, it could overlap with broader AWS infrastructure skills or other queue-related skills due to lack of specificity about what exactly it does. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a hollow template with no actual instructional content. It contains only meta-descriptions of what the skill would do without any concrete SQS queue setup guidance—no CLI commands, no CloudFormation/CDK examples, no configuration parameters, and no best practices. It provides zero value to Claude for performing SQS queue setup tasks.
Suggestions
Add concrete, executable examples: include AWS CLI commands (e.g., `aws sqs create-queue --queue-name MyQueue --attributes '{...}'`), CloudFormation YAML snippets, and/or CDK code for creating standard and FIFO queues.
Include a clear workflow with steps: 1) Create queue with appropriate settings, 2) Configure dead-letter queue, 3) Set IAM permissions/policies, 4) Validate with a test message send/receive cycle.
Add key configuration parameters and best practices: visibility timeout, message retention, encryption settings (SSE-SQS vs SSE-KMS), redrive policy configuration, and when to use Standard vs FIFO queues.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than teaching the task—these waste tokens on information Claude doesn't need.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual SQS queue setup instructions, commands, or configurations. Every token is wasted on describing the skill rather than teaching it. | 1 / 3 |
Actionability | There is zero concrete guidance—no AWS CLI commands, no CloudFormation templates, no CDK code, no SDK examples, no configuration parameters. The content only describes what it would do rather than actually doing it. | 1 / 3 |
Workflow Clarity | No workflow steps are provided at all. Setting up an SQS queue involves multiple steps (creating the queue, configuring dead-letter queues, setting permissions, etc.) but none are outlined or sequenced. | 1 / 3 |
Progressive Disclosure | There is no meaningful content to organize, no references to detailed guides, no links to related configuration files or examples. The structure exists but contains only boilerplate headings with no substance. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
4dee593
- 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.