Domotz Alert Profiles SKILL.md skillA
Domotz Alert Profiles from wyre-ai/msp-claude-plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wyre-ai/msp-claude-plugins/Domotz Alert Profiles@git:20260806.ad583a2Pins git:20260806.ad583a2 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wyre-ai/msp-claude-plugins
- Path
msp-claude-plugins/domotz/domotz/skills/alerts/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260806.ad583a2, committed Aug 6, 2026
- First version recorded
- Apr 5, 2026
- Size
- 6,783 bytes
- Repository stars
- 52
- License
- Apache-2.0
Domotz alerting configuration: what an alert profile defines, the two tools that read profiles and their per-device bindings, monitoring coverage audits, and the important limit — this server exposes alert configuration only, never fired alerts.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Domotz Alert Profiles ## Overview Domotz alert profiles define what conditions the platform watches and where it sends notifications when they trigger. This skill covers reading that configuration and auditing coverage across a site. ## What this server does NOT expose **There is no tool that returns a fired alert.** The Domotz MCP server registers exactly two alert tools, and both describe configuration: `domotz_alerts_profiles_list` (what profiles exist) and `domotz_alerts_device_list` (which profiles are bound to one device). Neither returns an alert instance, an alert ID, a severity, a timestamp, or an active/resolved state. There is no alert feed, no alert history, and no way to ask "what is alerting right now" through this integration. That is a limit worth stating rather than working around, because the obvious workaround is wrong in a specific way. You can approximate current site health from `domotz_devices_list` status plus `domotz_devices_history` and `domotz_devices_uptime` — but that is *device state*, not *alert state*. It will not tell you what Domotz notified on, whether anyone acknowledged it, or whether a profile was even bound to that device. Do not …
Read the whole file at its exact version.
How to install
mdr add wyre-ai/msp-claude-plugins/Domotz Alert Profiles@sha256:e2e5db4dd848855aThe line at the top of this page pins the label git:20260806.ad583a2, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_icgfsiaaftzcf76n)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Apr 5, 2026 and Aug 6, 2026, about one every 31 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260806.ad583a2 latest | 2026-08-06 | ad583a2 | 6,783 B | A | view · diff |
| git:20260804.055e86e | 2026-08-04 | 055e86e | 5,066 B | A | view · diff |
| git:20260728.b7e78fc | 2026-07-28 | b7e78fc | 4,582 B | A | view · diff |
| git:20260713.1fbd3f3 | 2026-07-13 | 1fbd3f3 | 4,601 B | A | view · diff |
| git:20260405.09d00fc | 2026-04-05 | 09d00fc | 4,614 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6783 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
wyre-ai/msp-claude-plugins · 52 stars · license Apache-2.0 · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_icgfsiaaftzcf76n GET https://markdownregistry.com/api/v1/resolve?ref=wyre-ai/msp-claude-plugins/Domotz Alert Profiles GET https://markdownregistry.com/api/v1/blob/e2e5db4dd848855acbf77163c32c84e5859b4e12c6a74a89a0860bd29754a5c5
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.