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 and essentially just restates the skill name with no additional detail. It lacks concrete actions, natural trigger terms, and any 'Use when...' guidance. The only redeeming quality is that 'SQS' is a specific enough service name to provide slight distinctiveness.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates and configures AWS SQS queues, sets up dead-letter queues, configures visibility timeouts, access policies, and FIFO queue settings.'
Add a 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a message queue, set up SQS, configure queue permissions, or work with AWS messaging infrastructure.'
Remove the duplicate trigger term 'sqs queue setup' and replace with varied natural language terms users might say, such as 'create queue', 'message queue', 'AWS SQS', 'queue configuration', 'FIFO queue'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'sqs queue setup' without listing any concrete actions like creating queues, configuring dead-letter queues, setting visibility timeouts, or defining access policies. It's extremely vague about what it actually does. | 1 / 3 |
Completeness | The 'what' is barely stated beyond the name itself, and the 'when' is missing entirely — there is no 'Use when...' clause or equivalent explicit trigger guidance. The description fails to answer either question meaningfully. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'sqs queue setup' repeated twice. Missing natural variations users would say like 'create SQS queue', 'message queue', 'AWS queue', 'FIFO queue', 'dead letter queue', 'SNS to SQS', etc. | 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 the lack of specificity about what exactly it covers. | 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: AWS CLI commands (`aws sqs create-queue --queue-name ...`), CloudFormation YAML snippets, or CDK code for creating standard and FIFO queues.
Include a clear workflow with steps: create queue, configure dead-letter queue, set visibility timeout/retention, configure IAM permissions, and validate with a test message send/receive.
Add SQS-specific best practices: FIFO vs standard queue selection criteria, dead-letter queue configuration, visibility timeout tuning, encryption settings, and access policy examples.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actual actionable content that teaches SQS queue setup.
| 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
933cf26
- 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.