Morning Run for Domotz

A shareable workflow that turns your Domotz environment into a one-prompt morning operations dashboard. Built for MSPs, internal NetOps teams, and anyone running Domotz at scale.

You ask Claude to “run it.” Claude executes ~18 health checks against your Domotz MCP server, then renders a single screenshot-ready HTML dashboard you can scan in two minutes.

This package contains everything you need to set it up.

---

What you get

1. morning-run-prompt.md — the system prompt that tells Claude what to check, how to triage, and how to render the dashboard. This is the heart of the workflow.
2. morning-run-setup.md — three ways to install it: paste-it (works today, zero setup), Claude Project (recommended daily flow), and Claude Code slash command (for terminal users).
3. This README — what the package is, what it does, what you need.

---

What it actually does

When you run the prompt against your Domotz environment, Claude executes 18 checks organized into three tiers:

Tier 1 — Critical (act now): offline important devices, active critical alerts, unhealthy collectors, long-running unresolved alerts, credential failures on managed infrastructure, new or unrecognized devices.

Tier 2 — Operational (act this week): stale data on devices that appear healthy, orphaned alert rules, stale or failed config backups, important devices with no alert coverage, SNMP coverage gaps, devices left in unmanaged state.

Tier 3 — Strategic (act this quarter, or sell as a service): sites without baseline monitoring, customers with alert noise that needs tuning, end-of-life or out-of-date firmware, sites without config backup enabled, tag and documentation gaps, fleet trend changes.

The output is a single HTML artifact with:

• A header showing date, time, organizations scanned, and device count
• A priority strip at the top with the 3 to 5 things actually worth acting on today
• Eighteen color-coded check cards organized by tier
• A “billable opportunities” strip near the bottom, surfacing findings you could turn into customer conversations, QBR slides, or new recurring revenue
• A timestamp and total runtime

Total runtime is typically 60 to 120 seconds, depending on the size of your environment.

---

What you need before you start

1. A Domotz account with at least one collector and some devices under monitoring. The richer your environment, the more the dashboard surfaces.
2. Access to Claude on one of these surfaces:
   • claude.ai (web)
   • Claude Desktop (macOS or Windows)
   • Claude Code (CLI, for the slash-command flow)
3. The Domotz MCP connector enabled in your Claude environment. Setup is in Claude under Settings → Connectors → search “Domotz.” You’ll be prompted to authorize against your Domotz account.

That’s it. No scripts to install, no API keys to manage, no servers to host. The MCP handles authentication and tool exposure.

---