mqtt-operator
The mqtt-operator skill enables safe MQTT topic interactions by enforcing allow/deny policies, treating publishes as write actions requiring explicit confirmation, and providing controlled read methods like subscribe_once for sampling or get_last when the event bridge is active. Use this skill when integrating with MQTT brokers while maintaining strict payload validation, preferring JSON over binary formats, and respecting configured topic restrictions.
git clone --depth 1 https://github.com/clawdotnet/openclaw.net /tmp/mqtt-operator && cp -r /tmp/mqtt-operator/src/OpenClaw.Gateway/skills/mqtt-operator ~/.claude/skills/mqtt-operatorSKILL.md
When interacting with MQTT: 1) Treat publishing as a “write” action: - Confirm the exact topic and payload semantics before publishing. 2) For reads: - Use `mqtt.subscribe_once` to sample a topic and confirm payload shape. - Use `mqtt.get_last` when the MQTT event bridge is enabled. 3) Keep payloads small and structured: - Prefer JSON payloads; avoid binary or huge strings. 4) Respect topic policies: - If a topic is denied by allow/deny globs, explain what’s blocked and suggest an allowed alternative.
Organizes repository documentation and keeps new docs in the correct location.
Produce a daily news brief (AI/security/dev) with links, key takeaways, and action items.
Connects to databases, runs SQL queries, and analyzes datasets using code to provide actionable business insights.
Conducts comprehensive web research, synthesizes data from multiple sources, and produces detailed reports.
Triage inbox into “needs reply”, “FYI”, “urgent”, and “safe to archive”, with a short plan for each.
Safely operate Home Assistant by resolving targets first and validating state before writes.
Operates as an autonomous software engineer, capable of writing code, running tests, and managing git repositories.