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.
88
82%
Does it follow best practices?
Impact
100%
1.21xAverage 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, provides specific capabilities, includes a clear 'Use when...' clause with multiple trigger scenarios, and uses terminology that users would naturally employ when working with AWS SQS.
| 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...') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'AWS SQS', 'message queue', 'queues', 'dead-letter queues', 'visibility timeouts', 'FIFO', 'Lambda' - good coverage of both service names and technical concepts users would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to AWS SQS with distinct triggers like 'SQS', 'dead-letter queues', 'visibility timeouts', 'FIFO ordering' - unlikely to conflict with other AWS or messaging skills due to SQS-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 SQS skill with excellent code examples covering the full lifecycle of queue operations. The main weaknesses are verbosity in the introduction, a monolithic structure that could be better split across files, and missing explicit validation checkpoints in multi-step workflows like DLQ setup and message processing.
Suggestions
Remove the introductory paragraph explaining what SQS is - Claude already knows this
Add explicit validation steps to multi-step workflows (e.g., 'Verify DLQ ARN was retrieved correctly before setting redrive policy')
Split CLI Reference and Troubleshooting sections into separate files (CLI_REFERENCE.md, TROUBLESHOOTING.md) with clear links from the main skill
Remove the Table of Contents - it consumes tokens without adding value for Claude's navigation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good use of tables and code examples, but includes some unnecessary explanations (e.g., 'Amazon Simple Queue Service (SQS) is a fully managed message queuing service...') and the Table of Contents adds tokens without much value for Claude. | 2 / 3 |
Actionability | Excellent executable code examples throughout - both AWS CLI and boto3 with complete, copy-paste ready snippets. Covers all major operations (create, send, receive, delete, DLQ configuration, Lambda integration) with specific commands and working code. | 3 / 3 |
Workflow Clarity | Individual operations are clear, but multi-step workflows like DLQ configuration lack explicit validation checkpoints. The receive/process loop shows error handling but doesn't include verification steps to confirm successful processing before deletion in complex scenarios. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but it's a monolithic document (~300 lines) that could benefit from splitting CLI reference and troubleshooting into separate files. References section points to external docs but no internal file references for advanced topics. | 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 | |
5df6da7
Table of Contents
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.