CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/rabbitmq-tests

Tests RabbitMQ producer/consumer interactions - supports AMQP 0.9.1 and AMQP 1.0 protocols across 6 tutorial patterns (Hello World, Work Queues, Publish/Subscribe, Routing, Topics, RPC) plus Publisher Confirms; consumer ack/nack/requeue patterns; durable queues + persistent messages; quorum vs classic queue; tests via Testcontainers RabbitMQ image or LocalStack-equivalent. Use when the user works with RabbitMQ producers/consumers (pika, amqplib, RabbitMQ.Client, spring-amqp) and needs unit/integration tests.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

A well-structured, highly actionable testing skill with executable code for every pattern and a clear step sequence. Its main weakness is the Overview section, which re-explains RabbitMQ basics and tutorial-pattern descriptions Claude already knows.

Suggestions

Trim the Overview: drop 'RabbitMQ is the leading OSS AMQP message broker' and the per-pattern tutorial table (Hello World = single producer→consumer, etc.), which restates knowledge Claude already has; keep only the enumerated pattern list that the tests map to.

Replace the prose quote from rabbitmq.com ('Executable versions of these tutorials [are open source]...') with a bare link to avoid explanation-style padding.

Consider moving the per-protocol/per-language detail (AMQP 0.9.1 vs 1.0, pika vs aio-pika) currently spread across Limitations into a single compact note, since the skill's examples are Python/0.9.1 only.

DimensionReasoningScore

Conciseness

Mostly efficient with tight code blocks, but the Overview explains concepts Claude already knows ('RabbitMQ is the leading OSS AMQP message broker' and a table describing what each tutorial pattern is), which is unnecessary padding.

2 / 3

Actionability

Provides fully executable Python fixtures and test bodies (Testcontainers setup, publish/consume, ack/nack, DLX, confirms, quorum) plus a copy-paste CI services block — copy-paste ready guidance.

3 / 3

Workflow Clarity

Steps 1–8 are clearly sequenced from approach selection through setup, each pattern, and CI; the tests themselves act as validation checkpoints and the Anti-patterns section gives error-recovery guidance.

3 / 3

Progressive Disclosure

No bundle files are present, so scoring is on organization: clearly headed sections (Overview, When to use, Steps 1–8, Anti-patterns, Limitations, References) with one-level-deep external URL references and no nested file chains.

3 / 3

Total

11

/

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.

A strong, third-person description that states concrete capabilities and provides an explicit 'Use when' trigger with natural library and protocol keywords. It is comprehensive yet not padded, and clearly distinguishable from sibling testing skills.

DimensionReasoningScore

Specificity

Lists many concrete actions and capabilities — 'consumer ack/nack/requeue patterns', 'durable queues + persistent messages', 'quorum vs classic queue', 'Publisher Confirms', plus six named tutorial patterns — matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly answers both what (tests the listed interaction/pattern sets) and when via the explicit 'Use when the user works with RabbitMQ producers/consumers ... and needs unit/integration tests' trigger, matching the top anchor.

3 / 3

Trigger Term Quality

Natural user-facing terms abound: 'RabbitMQ producers/consumers', the library names 'pika, amqplib, RabbitMQ.Client, spring-amqp', 'publisher confirms', and 'unit/integration tests' — strong coverage of what a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to RabbitMQ testing with protocol-specific and library-specific triggers, giving it a clear niche unlikely to fire for sibling message-broker skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents