CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mqtt-automation

Publish Aegis events to MQTT broker

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/automation/mqtt/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

The content is lean, well-structured, and gives executable setup guidance with a concrete events table. Its main gap is the absence of a usage/run example and an explicit verification checkpoint, which hold actionability and workflow clarity just below full marks.

Suggestions

Add a short runnable usage example showing how the script is invoked (e.g. feeding event JSON on stdin and the resulting MQTT topic).

Include a verification step after setup/connection, such as confirming the "ready" event or a test publish, to add an explicit checkpoint.

Briefly note configuration of the broker/port/credentials parameters so users know how to connect beyond the defaults.

DimensionReasoningScore

Conciseness

The body is lean — a one-line intro, a compact events table, and a three-line setup snippet — with no over-explanation of concepts Claude already knows, so every token earns its place.

5 / 5

Actionability

The setup commands (venv creation, pip install) are concrete and executable, and the events table is specific, but no run/usage example showing how to actually invoke the publisher is included, leaving a minor gap.

4 / 5

Workflow Clarity

This single-purpose skill has an unambiguous core action (publish the listed events to MQTT topics), but the body shows no explicit verification checkpoint for the connection or publish step, keeping it just below 5.

4 / 5

Progressive Disclosure

The under-50-line body is well-organized into clear sections (intro, Events Published table, Setup) with no need for external references; the companion script lives appropriately in scripts/ and is referenced from the frontmatter.

5 / 5

Total

18

/

20

Passed

Description

53%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.

The description is concise and names a specific niche, but it is incomplete: it states what the skill does without any "Use when..." trigger guidance and with limited keyword coverage. Adding explicit trigger conditions and a couple more concrete actions would lift several dimensions.

Suggestions

Add a "Use when..." clause naming concrete triggers, e.g. "Use when integrating Aegis with Home Assistant, Node-RED, or any MQTT automation platform."

Expand the action list beyond "publish" to be more comprehensive, e.g. mention which events are published or that it bridges camera events to MQTT topics.

Include natural synonyms and platform terms users would say (MQTT, Home Assistant, automation, smart home) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The phrase "Publish Aegis events to MQTT broker" names the domain (Aegis events, MQTT) and one concrete action (publish), but lists no further specific actions, matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

It states a clear "what" (publish Aegis events to an MQTT broker) but provides no "Use when..." trigger clause, so per the rubric the missing explicit trigger guidance caps completeness at 3.

3 / 5

Trigger Term Quality

"MQTT", "events", and "broker" are relevant keywords a user might say, but common variations and consumer-platform terms (Home Assistant, automation, Node-RED) are missing, so it does not reach good coverage.

3 / 5

Distinctiveness Conflict Risk

The Aegis-plus-MQTT niche is mostly distinct with only minor overlap risk against other automation skills, though the absence of distinct trigger phrases keeps it just below a 5.

4 / 5

Total

13

/

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.

Validation — 15 / 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

SharpAI/DeepCamera

Path

skills/automation/mqtt/SKILL.md

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.