Qdrant Monitoring
github/awesome-copilot
Guides Qdrant monitoring and observability setup. An agent skill from github/awesome-copilot.
Device availability and monitored inventory from Zabbix — is a device reachable, since when, how often has it flapped, and what is the NMS actually watching.
$ npx skills add automateyournetwork/netclaw --skill zabbix-availability -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install automateyournetwork/netclaw zabbix-availability --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/workspace/skills/zabbix-availability .claude/skills/zabbix-availability && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "zabbix-availability" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/zabbix-availability into .claude/skills/zabbix-availability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zabbix-availability", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/zabbix-availabilityType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add automateyournetwork/netclaw --skill zabbix-availability -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install automateyournetwork/netclaw zabbix-availability --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/workspace/skills/zabbix-availability .agents/skills/zabbix-availability && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "zabbix-availability" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/zabbix-availability into .agents/skills/zabbix-availability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zabbix-availability", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add automateyournetwork/netclaw --skill zabbix-availability -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install automateyournetwork/netclaw zabbix-availability --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/workspace/skills/zabbix-availability .cursor/skills/zabbix-availability && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "zabbix-availability" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/zabbix-availability into .cursor/skills/zabbix-availability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zabbix-availability", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/automateyournetwork/netclaw.git --path workspace/skills/zabbix-availability--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add automateyournetwork/netclaw --skill zabbix-availability -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install automateyournetwork/netclaw zabbix-availability --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/workspace/skills/zabbix-availability .gemini/skills/zabbix-availability && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "zabbix-availability" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/zabbix-availability into .gemini/skills/zabbix-availability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zabbix-availability", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install automateyournetwork/netclaw zabbix-availabilityInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add automateyournetwork/netclaw --skill zabbix-availability -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/workspace/skills/zabbix-availability .github/skills/zabbix-availability && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "zabbix-availability" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/zabbix-availability into .github/skills/zabbix-availability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zabbix-availability", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add automateyournetwork/netclaw --skill zabbix-availability -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install automateyournetwork/netclaw zabbix-availability --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/workspace/skills/zabbix-availability .opencode/skills/zabbix-availability && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "zabbix-availability" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/zabbix-availability into .opencode/skills/zabbix-availability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zabbix-availability", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
zabbix-availabilityDevice availability and monitored inventory from Zabbix — is a device reachable, since when, how often has it flapped, and what is the NMS actually watching.
Zabbix Availability is an agent skill from automateyournetwork/netclaw. Device availability and monitored inventory from Zabbix — is a device reachable, since when, how often has it flapped, and what is the NMS actually watching. Use when someone asks how long a device has been down, whether it is flapping, or what is and is not being monitored.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: An AI agent that claws through your network. The licence is Apache-2.0.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 95bb17e. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are jsonc).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Zabbix Availability loads about 1.2k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 541 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from automateyournetwork/netclaw at commit 95bb17e, republished under its Apache-2.0 licence (© automateyournetwork). 541 words, ~1,239 tokens.
.claude/skills/zabbix-availability/SKILL.md (or your agent's skills folder).zabbix-mcp — vendored third-party, read-only, three tools. See
zabbix-metrics-history for the shared cautions.
"Zabbix cannot reach it" is not "the device is down."
An NMS reports what one poller saw, from one vantage point, at one polling interval. That is evidence, not a verdict.
A device can be unreachable from Zabbix and completely healthy: a firewall rule, a management-VRF problem, a dead SNMP daemon on an otherwise forwarding router, or a poller that has simply not tried recently.
Never write "the device is down." Write:
"Zabbix has been unable to reach rtr-01 since 14:02 UTC. That is the monitoring system's view from its own vantage point — it is not confirmation the device is down.
pyatsormultivendor-clican check the device directly."
This is the same discipline globalping-external-checks applies to probes, and it matters more here,
because an NMS feels authoritative in a way a probe network does not.
| State | available | Say |
|---|---|---|
| Reachable | 1 | "Zabbix reached it at <time>" |
| Unreachable | 2 | "Zabbix cannot reach it as of <time>" — never "it is down" |
| Unknown | 0 | "Zabbix has not yet established reachability" — not the same as unreachable |
| Not monitored | host absent | "this device is not monitored by Zabbix" — not the same as unreachable, and by far the most common cause of surprise |
zabbix_api("host.get", {
"output": ["hostid","host","name","status"],
"selectInterfaces": ["interfaceid","ip","dns","port","available","error","errors_from"],
"selectTags": "extend"
})Availability without a timestamp is a claim about the present that may be minutes or hours stale. Every
answer states when that state was last observed. errors_from gives you when the failure began.
"It has been down for 40 minutes" and "it has bounced nine times in 40 minutes" lead to completely
different investigations. Get the transitions, not just the current state — event.get against the
unreachability trigger gives you the history.
Report the count of transitions as well as the current state whenever the window contains more than one.
zabbix_api("host.get", {"output":["hostid","host","status"], "selectInterfaces":"extend",
"selectParentTemplates":["name"], "selectHostGroups":["name"]})
zabbix_api("hostgroup.get", {"output":"extend"})
zabbix_api("item.get", {"hostids":["<id>"],
"output":["itemid","name","key_","value_type","units","history","trends","lastclock"]})Two rules:
status: 1) is shown as disabled, never omitted. A device nobody is watching is a
finding, not an absence — it is usually how a gap in monitoring is discovered.history, trends). This lets an engineer see how far
back a question can be answered before they ask it, which is far better than asking and getting nothing.An item whose lastclock is empty is monitored but has never returned a value — a broken poll, and a
real finding. Do not report it as "no data".
| Want to… | Use |
|---|---|
| Metric values over time | zabbix-metrics-history |
| Problems and alerts | zabbix-problem-review |
| Unsolicited traps | snmptrap-mcp — push, not poll |
| Flows | ipfix-mcp |
| Instrumented metrics | prometheus, grafana |
| SaaS monitoring | auvik, thousandeyes, datadog |
| Confirm whether a device is actually down | pyats, multivendor-cli, fortinet — go ask the device. This skill only reports what the poller saw |
| Add, enable or disable a host | nothing here. Read-only; NMS configuration is out of scope entirely |
© automateyournetwork, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in workspace/skills/zabbix-availability of automateyournetwork/netclaw.
Open the folder on GitHubat commit 95bb17e
Zabbix Availability next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Zabbix Availability this skillautomateyournetwork/netclaw | 676 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Qdrant Monitoringgithub/awesome-copilot | 40k | 1 repos | ~276 | Automated safety check: Pass | MIT | |
| Monitoring Capture ServicePostHog/posthog | 40k | — | ~5k | Automated safety check: Pass | Custom licence | |
| Monitoring Ingestion PipelinePostHog/posthog | 40k | — | ~9.1k | Automated safety check: Pass | Custom licence | |
| Foundation Models On Deviceaffaan-m/ECC | 276k | 4 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Agent Performance Monitorruvnet/ruflo | 74k | 2 repos | ~4.9k | Automated safety check: Pass | MIT |
github/awesome-copilot
Guides Qdrant monitoring and observability setup. An agent skill from github/awesome-copilot.
PostHog/posthog
Guide for using the Grafana MCP to monitor and diagnose the capture service (rust/capture) in production.
PostHog/posthog
Guide for using the Grafana MCP to monitor and diagnose the Node.js ingestion pipeline workers in production.
affaan-m/ECC
Apple FoundationModels framework for on-device LLM — text generation, guided generation with @Generable, tool calling, and snapshot streaming in iOS 26+.
ruvnet/ruflo
Agent skill for performance-monitor - invoke with $agent-performance-monitor
ruvnet/ruflo
Stream live swarm events using the Monitor tool for real-time observability
automateyournetwork/netclaw
Entry point for designing EVE-NG network labs: classifies the request, gathers missing requirements, proposes options and validates the resulting topology.
automateyournetwork/netclaw
Deploys Cisco ACI policy changes only behind an approved ServiceNow Change Request, capturing pre and post-change fault baselines and rolling back automatically on a fault delta.
automateyournetwork/netclaw
Runs a phased health audit of a Cisco ACI fabric through MCP tools: node status, links, tenant and policy review, faults and endpoint learning.
automateyournetwork/netclaw
Validate Arista EOS network state against ANTA's pre-built 208-test catalogue, with structured pass/fail verdicts.
automateyournetwork/netclaw
Arista CloudVision Portal (CVP) automation via REST API — device inventory, events, connectivity monitoring, tag management (4 tools).
automateyournetwork/netclaw
AWS CloudWatch monitoring — metrics, alarms, log queries, VPC flow log analysis, network performance.
Device availability and monitored inventory from Zabbix — is a device reachable, since when, how often has it flapped, and what is the NMS actually watching. Zabbix Availability is an agent skill from automateyournetwork/netclaw. Device availability and monitored inventory from Zabbix — is a device reachable, since when, how often has it flapped, and what is the NMS actually watching.
Zabbix Availability fits situations like: someone asks how long a device has been down; whether it is flapping; what is and is not being monitored.
Run `npx skills add automateyournetwork/netclaw --skill zabbix-availability -a claude-code`. Or copy the skill folder (workspace/skills/zabbix-availability in automateyournetwork/netclaw) into .claude/skills/zabbix-availability in your project. Claude Code loads it when a task matches its description.
Run `npx skills add automateyournetwork/netclaw --skill zabbix-availability -a codex`. Or copy the skill folder (workspace/skills/zabbix-availability in automateyournetwork/netclaw) into .agents/skills/zabbix-availability in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add automateyournetwork/netclaw --skill zabbix-availability -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/zabbix-availability, .gemini/skills/zabbix-availability, .github/skills/zabbix-availability and .opencode/skills/zabbix-availability in your project.
SKILL.md names no scripts, command-line tools or credentials: Zabbix Availability is instructions for the agent only. Our summary lists: A credential in ZABBIX_TOKEN.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Zabbix Availability is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Zabbix Availability: Qdrant Monitoring (github/awesome-copilot, 40k stars), Monitoring Capture Service (PostHog/posthog, 40k stars), Monitoring Ingestion Pipeline (PostHog/posthog, 40k stars) and Foundation Models On Device (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
automateyournetwork (a GitHub user) maintains it in automateyournetwork/netclaw, which has 676 GitHub stars. The repository holds 120 skills in this directory. The repository was last updated on October 5, 2026.
Source: automateyournetwork/netclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.