mqtt-automation

Publish Aegis events to MQTT broker

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/automation/mqtt/SKILL.md

Quality

Content

72%

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

The body is clean, concise, and well-structured with a clear events table and one-level reference to the publish script, but it stops at setup and never tells Claude how to run the skill or verify the broker connection, leaving actionability and workflow clarity incomplete.

Suggestions

Add a short 'Usage' section with the executable run command and key arguments (e.g. broker, port, topic_prefix) so the core task is copy-paste ready.

Include a brief verification step, such as confirming the 'ready' event appears or testing the connection, to give the setup workflow an explicit checkpoint.

Optionally show one example published payload so the expected topic/payload shape is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean (~20 lines): a one-line intro, a compact events table, and a setup block, with no padding or explanation of concepts Claude already knows; every section earns its place, matching the 'lean and efficient' anchor.	3 / 3
Actionability	The Setup block (venv + pip install) is concrete and executable, but the body never shows how to actually run the skill or publish an event (no invocation command, arguments, or example payload), so guidance is incomplete; not score 3 because it is not copy-paste ready for the core task.	2 / 3
Workflow Clarity	A setup sequence is present (create venv, install deps) but the body omits the run/launch step and any checkpoint verifying the broker connection works; though it is a simple single-task skill, the missing execution step keeps it at 'sequence present but checkpoints missing', below score 3.	2 / 3
Progressive Disclosure	The skill is under 50 lines with well-organized sections (Events Published, Setup) and a single one-level-deep bundle reference (scripts/mqtt_publish.py declared in frontmatter capabilities); per the scoring notes this satisfies progressive disclosure for a simple skill without nested references.	3 / 3
	Total	10 / 12 Passed

Description

57%

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 clear, distinctive niche but only partially complete: it states what the skill does without any explicit when-to-use trigger guidance and with limited trigger-term coverage.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when you want to send Aegis camera events to Home Assistant, Node-RED, or an MQTT broker.'

Broaden natural trigger terms to include phrasings a user would actually say, such as 'MQTT', 'Home Assistant', 'Node-RED', or 'smart home automation'.

Name additional concrete actions (e.g. publishing clip, person-detection, and alert events to per-camera topics) to raise specificity.

Dimension	Reasoning	Score
Specificity	"Publish Aegis events to MQTT broker" names the domain (Aegis events, MQTT broker) and one concrete action (publish), but does not list multiple specific concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	The description answers what it does ("Publish Aegis events to MQTT broker") but provides no "Use when..." clause or equivalent explicit trigger guidance; per the judging guidelines a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	"MQTT broker" is a natural term a user would say, and "Aegis events" is domain-relevant, but coverage is thin and misses common variations, matching 'some relevant keywords but missing common variations'; not score 3 because it lacks the breadth of natural trigger phrasings.	2 / 3
Distinctiveness Conflict Risk	The pairing of the specific Aegis product with the MQTT protocol defines a clear niche unlikely to trigger for unrelated skills; it is above score 2 ('could still overlap with similar skills') because the domain is narrowly scoped rather than generic.	3 / 3
	Total	9 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 2264fcb

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.