sqs
AWS SQS message queue service for decoupled architectures. Use when creating queues, configuring dead-letter queues, managing visibility timeouts, implementing FIFO ordering, or integrating with Lambda.
85
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillAgent success when using this skill
Validation for skill structure
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 excels across all dimensions. It uses third person voice, provides specific concrete actions, includes natural trigger terms that users would actually say, and has an explicit 'Use when...' clause with clear triggers. The AWS SQS-specific terminology makes it highly distinctive and unlikely to conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'creating queues, configuring dead-letter queues, managing visibility timeouts, implementing FIFO ordering, integrating with Lambda' - these are all distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('AWS SQS message queue service for decoupled architectures') and when ('Use when creating queues, configuring dead-letter queues, managing visibility timeouts, implementing FIFO ordering, or integrating with Lambda') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'AWS SQS', 'message queue', 'dead-letter queues', 'visibility timeouts', 'FIFO', 'Lambda'. These cover both the service name and common configuration terms users would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with AWS SQS-specific terminology (dead-letter queues, visibility timeouts, FIFO ordering) that clearly separates it from other AWS services or generic messaging skills. | 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 SQS skill with excellent executable code examples covering all major use cases. The main weaknesses are verbosity in the introduction and reference sections, plus a monolithic structure that could benefit from splitting detailed reference material into separate files. Workflow clarity could be improved with explicit validation checkpoints.
Suggestions
Remove the introductory paragraph explaining what SQS is - Claude already knows this
Add explicit validation steps after queue creation and DLQ configuration (e.g., 'Verify: aws sqs get-queue-attributes...')
Split CLI Reference and Troubleshooting sections into separate reference files to reduce main skill length
Remove the Table of Contents - it adds tokens without significant navigation value in a skill file
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary content like the introductory paragraph explaining what SQS is (Claude knows this) and the table of contents which adds little value. The tables and reference sections are useful but could be trimmed. | 2 / 3 |
Actionability | Excellent executable code examples throughout - both AWS CLI and boto3 Python code are copy-paste ready with realistic queue URLs, proper JSON formatting, and complete working patterns for all common operations. | 3 / 3 |
Workflow Clarity | Multi-step processes like DLQ configuration show the sequence but lack explicit validation checkpoints. The receive/process loop shows error handling but doesn't emphasize verification steps. The troubleshooting section helps but workflows could benefit from explicit 'verify this worked' steps. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in one monolithic file. The CLI Reference tables and extensive troubleshooting could be split into separate reference files. External links are provided but internal progressive disclosure is missing. | 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 | |
- 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.