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.

1.21x

Quality

82%

Does it follow best practices?

Impact

100%

1.21x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

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 reference for AWS SQS with excellent executable code examples in both CLI and Python. Its main weaknesses are verbosity (explaining what SQS is, including full CLI reference tables that duplicate docs) and lack of explicit validation checkpoints in multi-step workflows like DLQ configuration. The monolithic structure would benefit from splitting reference material into separate files.

Suggestions

Remove the introductory paragraph explaining what SQS is and the Table of Contents—Claude already knows SQS and can navigate the document without it.

Add validation steps after key operations (e.g., verify queue creation with get-queue-attributes, confirm redrive policy is set correctly after DLQ configuration).

Move the CLI Reference tables and detailed troubleshooting into separate bundle files (e.g., CLI_REFERENCE.md, TROUBLESHOOTING.md) to keep the main skill lean.

Dimension	Reasoning	Score
Conciseness	The skill is fairly comprehensive but includes some unnecessary content Claude already knows (e.g., the opening paragraph explaining what SQS is, the Table of Contents for a single file, and the CLI Reference tables that essentially duplicate AWS documentation). The core concepts tables are borderline—useful as quick reference but some of it is basic knowledge.	2 / 3
Actionability	Excellent executable examples throughout—both CLI commands and boto3 Python code are copy-paste ready with realistic parameters. The DLQ configuration, send/receive patterns, Lambda integration, and troubleshooting debug commands are all concrete and complete.	3 / 3
Workflow Clarity	The DLQ configuration shows a clear multi-step sequence (create DLQ → get ARN → set redrive policy), and the receive-and-process pattern includes error handling with delete-on-success. However, there are no explicit validation checkpoints—e.g., after creating a queue there's no verification step, and the DLQ setup doesn't verify the redrive policy was applied correctly.	2 / 3
Progressive Disclosure	The content is a monolithic single file with no bundle files to reference. At ~250 lines, the CLI reference tables and some of the troubleshooting content could be split into separate files. The internal Table of Contents helps navigation but the file is longer than it needs to be for a skill overview.	2 / 3
	Total	9 / 12 Passed

Description

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 strong skill description that concisely identifies the domain (AWS SQS), lists specific capabilities, and provides an explicit 'Use when...' clause with natural trigger terms. It uses proper third-person voice and covers both common and advanced SQS use cases, making it highly distinguishable from other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: creating queues, configuring dead-letter queues, managing visibility timeouts, implementing FIFO ordering, and integrating with Lambda.	3 / 3
Completeness	Clearly answers both 'what' (AWS SQS message queue service for decoupled architectures) and 'when' (explicit 'Use when...' clause listing five specific trigger scenarios).	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'SQS', 'message queue', 'dead-letter queues', 'visibility timeouts', 'FIFO ordering', 'Lambda', and 'decoupled architectures'. These cover the main terms a user working with SQS would naturally use.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with SQS-specific terminology like 'dead-letter queues', 'visibility timeouts', 'FIFO ordering', and 'message queue'. Unlikely to conflict with other AWS service skills or general messaging skills.	3 / 3
	Total	12 / 12 Passed

Validation

90%

Warnings & errors only

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

Repository: itsmostafa/aws-agent-skills
Commit: 4ab904a

Reviewed: about 1 month ago

Table of Contents

Discovery Implementation Validation

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.