CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

88

1.21x
Quality

82%

Does it follow best practices?

Impact

100%

1.21x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thorough, highly actionable SQS reference with executable code throughout, but it is a monolithic inlined document rather than a lean overview pointing to separate reference files, and it lacks explicit validation checkpoints for destructive/batch operations.

Suggestions

Move the CLI Reference and Troubleshooting sections into separate bundle files (e.g. references/cli-reference.md, references/troubleshooting.md) and link to them one level deep from SKILL.md.

Add explicit validation steps for destructive/batch operations — e.g. verify queue attributes after create-queue, and confirm/prompt before purge-queue or delete-queue.

Trim the opening explanatory sentence about what SQS is, since Claude already knows the service; lead directly with the actionable content.

DimensionReasoningScore

Conciseness

Mostly efficient reference material — tables and executable code dominate — but the opening 'what SQS is' sentence and a few explanatory comments restate concepts Claude already knows and could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready AWS CLI and boto3 examples cover the common cases (create, send, receive, FIFO, DLQ, Lambda integration) with concrete attribute values.

5 / 5

Workflow Clarity

Sequences exist (e.g. DLQ setup: create → get ARN → set redrive policy) but there are no explicit validation checkpoints, and destructive/batch operations like purge-queue lack verification — capping this at 3 per the rubric.

3 / 5

Progressive Disclosure

Has a TOC and clear section headers, but ~330 lines of CLI reference tables and troubleshooting are inlined in SKILL.md with no bundle files to offload the bulk reference material.

3 / 5

Total

15

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states the service domain and provides explicit, varied 'Use when' triggers covering the main SQS tasks. Minor additional synonyms would push trigger quality to full marks.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'creating queues, configuring dead-letter queues, managing visibility timeouts, implementing FIFO ordering, or integrating with Lambda' — giving comprehensive coverage of SQS capabilities.

5 / 5

Completeness

Explicitly answers both 'what' ('AWS SQS message queue service for decoupled architectures') and 'when' ('Use when creating queues... or integrating with Lambda') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural terms (queues, dead-letter queues, FIFO ordering, visibility timeouts, Lambda) that AWS users would say, but a few common variations (e.g. 'message', 'polling', 'batch') are absent.

4 / 5

Distinctiveness Conflict Risk

Clear SQS-specific niche with distinct triggers; minimal overlap risk given the explicit AWS SQS framing and Lambda integration scope.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
itsmostafa/aws-agent-skills
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.