CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/stomp-amqp-tests

Tests STOMP over WebSocket (Spring, ActiveMQ, RabbitMQ Web STOMP) and AMQP 0-9-1 (RabbitMQ Java client) - frame connect/subscribe/send/ack sequences, ack modes (auto/client/client-individual), exchange and queue declarations, binding routing, Testcontainers RabbitMQ broker, and delivery assertion. Use when validating enterprise Spring or RabbitMQ messaging stacks before deploy.

74

Quality

93%

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.

The body is highly actionable with executable code, a clear sequenced workflow, and clean section organization. Its only weakness is conciseness, as repeated spec/doc quotations and "Per the [spec]" framing add tokens beyond the lean ideal.

Suggestions

Trim or paraphrase the long spec/doc quotations (e.g., the heart-beat negotiation quote in Step 2 and the confirms-doc sentences in Step 6) to the essential rule, keeping citations as links.

Reduce the repeated "Per the [STOMP 1.2 spec]/[rabbitmq.com/docs/...]" lead-in at the start of every step; link once per topic and lead with the actionable instruction instead.

Consider consolidating the duplicated STOMP-spec link references (Steps 2 and 3 both re-cite the full spec inline) to shave repeated tokens.

DimensionReasoningScore

Conciseness

Mostly efficient and free of basic-concept padding, but repeatedly quotes spec/doc sentences at length (heart-beat negotiation quote, confirms doc quotes) and prefixes nearly every step with "Per the [spec]" framing that could be tightened, matching the score-2 anchor rather than the lean score-3 anchor.

2 / 3

Actionability

Provides fully executable Java (ConnectionFactory, channel declares, basicPublish, basicConsume, basicQos, confirmSelect/waitForConfirms), a JS browser client, and a Maven XML dependency with real calls and assertions, matching the copy-paste-ready score-3 anchor rather than the pseudocode score-2 anchor.

3 / 3

Workflow Clarity

Seven numbered steps are clearly sequenced with a When-to-use preamble and an end-to-end bridge example, and each step's assertThat calls serve as explicit validation checkpoints against an ephemeral Testcontainers broker, matching the score-3 anchor.

3 / 3

Progressive Disclosure

No local bundle files exist; the body is well-organized into clearly signaled sections (When to use, Steps 1-7, Example, Anti-patterns, Limitations, References) with a one-level References section pointing to authoritative docs, matching the well-signaled score-3 anchor rather than the score-2 anchor.

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.

The description is specific, third-person, and provides both a comprehensive what-list and an explicit Use-when trigger. It clearly distinguishes a precise messaging-protocol niche from generic skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions ("frame connect/subscribe/send/ack sequences", "ack modes (auto/client/client-individual)", "exchange and queue declarations, binding routing", "Testcontainers RabbitMQ broker"), matching the score-3 anchor rather than the score-2 anchor which only names a domain and some actions.

3 / 3

Completeness

Explicitly answers both what (the enumerated action list) and when ("Use when validating enterprise Spring or RabbitMQ messaging stacks before deploy"), matching the score-3 anchor with an explicit trigger clause rather than score-2 where when is missing or implied.

3 / 3

Trigger Term Quality

Includes natural terms users would say (STOMP, WebSocket, RabbitMQ, Spring, AMQP, "messaging stacks", "before deploy") with good coverage, matching the score-3 anchor rather than score-2 which is missing common variations.

3 / 3

Distinctiveness Conflict Risk

Names a clear niche (STOMP over WebSocket + AMQP 0-9-1 on Spring/RabbitMQ stacks) in third person with distinct triggers unlikely to fire for the wrong skill, matching the score-3 anchor rather than score-2 which could still overlap.

3 / 3

Total

12

/

12

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents