CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/mqtt-tests

Test MQTT v5.0 with Mosquitto broker in CI + paho-mqtt clients - QoS 0 / 1 / 2 delivery semantics, retained messages, Last Will and Testament (LWT), shared subscriptions ($share/group/topic), $SYS topic introspection. Critical for IoT, embedded, and M2M systems where wire-level guarantees matter. Use when a product speaks MQTT on the wire and QoS 1 / 2 redelivery, retained-message state, or LWT behavior needs a broker-backed test - including smoke-testing a new broker auth / ACL / persistence config.

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.

A well-structured, actionable skill body: executable code, a numbered cross-referenced workflow with assert-based validation, and a properly split one-level reference. The only weakness is conciseness - the Worked example duplicates Step 3's QoS-1 redelivery walkthrough.

Suggestions

Remove or compress the 'Worked example' section, since it re-derives the same sensors/temp QoS-1 redelivery scenario already shown in Step 3; if kept, point to Step 3 instead of restating the full sequence.

Trim the QoS table's right-hand 'Use' column or the generic at-most/at-least/exactly-once framing, which Claude already knows; keep only the MQTT-specific handshake detail (e.g. PUBREC/PUBREL/PUBCOMP).

Consider folding the Anti-patterns fixes back into their referenced steps so the table can shrink to the pattern + why-it-fails columns.

DimensionReasoningScore

Conciseness

Mostly efficient executable code and targeted MQTT-specific gotchas (e.g. 'clean_start=False is required for the broker to retain offline session state'), but the 'Worked example' section largely re-walks the Step 3 QoS-1 redelivery scenario and the QoS table re-explains well-known at-most/at-least/exactly-once semantics, so it could be tightened.

2 / 3

Actionability

Fully executable, copy-paste-ready material throughout: GitHub Actions service block, mosquitto.conf, and paho-mqtt v5 client code with exact API calls (callback_api_version=VERSION2, clean_start=False, .wait_for_publish(), reconnect()).

3 / 3

Workflow Clarity

A clearly numbered, cross-referenced sequence ('How to use' Steps 1-6 linking to detailed Step sections) with explicit verification via test assertions (e.g. 'assert b"22.5" in received') and a supporting Anti-patterns table; not a destructive/batch context so assert-based checkpoints suffice.

3 / 3

Progressive Disclosure

Clear overview in SKILL.md with advanced behaviors (LWT, shared subscriptions, $SYS) split into a real, well-signaled one-level-deep reference (references/lwt-shared-subs-sys.md, linked twice in the body) - easy navigation, no nested references.

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, specific description: it names concrete MQTT v5.0 testing surfaces, uses natural trigger vocabulary, and gives an explicit 'Use when' clause in third person. It is clearly distinguishable from neighboring realtime/protocol skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions - 'QoS 0 / 1 / 2 delivery semantics, retained messages, Last Will and Testament (LWT), shared subscriptions ($share/group/topic), $SYS topic introspection' plus 'smoke-testing a new broker auth / ACL / persistence config' - rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('Test MQTT v5.0 with Mosquitto broker in CI + paho-mqtt clients ...') and when via a clear 'Use when a product speaks MQTT on the wire and QoS 1 / 2 redelivery, retained-message state, or LWT behavior needs a broker-backed test ...' clause.

3 / 3

Trigger Term Quality

Covers natural terms a user would say - 'MQTT', 'Mosquitto', 'paho-mqtt', 'QoS', 'retained messages', 'LWT', 'shared subscriptions', '$SYS', 'broker' - with good breadth of the relevant vocabulary.

3 / 3

Distinctiveness Conflict Risk

A clear niche (MQTT v5.0 wire-level broker-backed testing with Mosquitto/paho-mqtt) with distinct triggers, unlikely to fire for unrelated skills; alternatives (websocket-tests, webhook-replay-tests) are explicitly distinct.

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