Is This A Problem
anthropics/claude-for-legal
Fast "is this a problem?" answer for the quick Slack question — pattern-matches against your calibration.
Review current and historical problems from Zabbix — severity, which host, when it started, how long it has been active, and whether anyone has acknowledged it.
Apache-2.0Auto-check passed
Install Zabbix Problem Review
$ npx skills add automateyournetwork/netclaw --skill zabbix-problem-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install automateyournetwork/netclaw zabbix-problem-review --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-problem-review .claude/skills/zabbix-problem-review && 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-problem-review" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/zabbix-problem-review into .claude/skills/zabbix-problem-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zabbix-problem-review", 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-problem-reviewType 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-problem-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install automateyournetwork/netclaw zabbix-problem-review --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-problem-review .agents/skills/zabbix-problem-review && 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-problem-review" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/zabbix-problem-review into .agents/skills/zabbix-problem-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zabbix-problem-review", 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-problem-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install automateyournetwork/netclaw zabbix-problem-review --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-problem-review .cursor/skills/zabbix-problem-review && 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-problem-review" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/zabbix-problem-review into .cursor/skills/zabbix-problem-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zabbix-problem-review", 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-problem-review--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-problem-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install automateyournetwork/netclaw zabbix-problem-review --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-problem-review .gemini/skills/zabbix-problem-review && 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-problem-review" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/zabbix-problem-review into .gemini/skills/zabbix-problem-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zabbix-problem-review", 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-problem-reviewInstalls 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-problem-review -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-problem-review .github/skills/zabbix-problem-review && 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-problem-review" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/zabbix-problem-review into .github/skills/zabbix-problem-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zabbix-problem-review", 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-problem-review -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-problem-review --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-problem-review .opencode/skills/zabbix-problem-review && 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-problem-review" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/zabbix-problem-review into .opencode/skills/zabbix-problem-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "zabbix-problem-review", 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.
Facts
- Skill name
zabbix-problem-review- GitHub stars
- 676
- Token cost
- ~1.1k tokens
- SKILL.md length
- 494 words
- Files
- 1
- Skills in repo
- 120
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Review current and historical problems from Zabbix — severity, which host, when it started, how long it has been active, and whether anyone has acknowledged it.
- Works in 5 steps: Never report an unreachable NMS as "no… → Always give duration, not just onset. → Acknowledged ≠ resolved. Say… → …
- Someone asks what is broken right now
- SKILL.md covers Server, Current problems vs history —…, The distinction that matters… and Acknowledgement is a workflow…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Zabbix Problem Review is an agent skill from automateyournetwork/netclaw. Review current and historical problems from Zabbix — severity, which host, when it started, how long it has been active, and whether anyone has acknowledged it. Use when someone asks what is broken right now, how long something has been broken, or what happened during a window that has already passed.
Its SKILL.md is about 1.1k 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.
When your agent uses it
- Someone asks what is broken right now
- How long something has been broken
- What happened during a window that has already passed
Example prompts
- “/zabbix-problem-review”
Requirements
- A credential in ZABBIX_TOKEN
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Never report an unreachable NMS as "no problems".
- Always give duration, not just onset.
- Acknowledged ≠ resolved. Say "acknowledged", never imply "handled".
- Say what you filtered out.
- Read-only. Acknowledging an alert is a real action a human owns; there is no write path here.
What it can do on your machine
Read from SKILL.md and the folder at commit aa90e7d. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
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.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Zabbix Problem Review loads about 1.1k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 494 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from automateyournetwork/netclaw at commit aa90e7d, republished under its Apache-2.0 licence (© automateyournetwork). 494 words, ~1,099 tokens.
Download SKILL.mdSave it as
.claude/skills/zabbix-problem-review/SKILL.md (or your agent's skills folder).- name
- zabbix-problem-review
- description
- Review current and historical problems from Zabbix — severity, which host, when it started, how long it has been active, and whether anyone has acknowledged it. Use when someone asks what is broken right now, how long something has been broken, or what happened during a window that has already passed.
- version
- 1.0.0
- license
- Apache-2.0
- tags
- zabbix, nms, monitoring, alerts, problems, incidents, triage, observability
- user-invocable
- true
Zabbix Problem Review
Server
zabbix-mcp — vendored third-party, read-only, three tools. See
zabbix-metrics-history for the shared cautions.
Current problems vs history — use the right one
| Question | Method | Note |
|---|---|---|
| What is wrong now? | problem.get | Reads a dedicated problem table. This is the right one |
| What happened then? | event.get | Historical, heavier, needs a time window |
| What rule fired it? | trigger.get | The definition behind a problem |
zabbix_api("problem.get", {
"output": "extend", "selectAcknowledges": "extend", "selectTags": "extend",
"recent": false, "sortfield": ["eventid"], "sortorder": "DESC"
})Every problem you report carries: severity · host · when it started · how long it has been active · acknowledgement state. "How long" is the question NetClaw could not answer at all before this integration existed — do not drop it.
The distinction that matters most here
"No active problems" and "the NMS could not be reached" are not the same answer.
An empty problem list is a legitimate, positive finding — the monitoring system looked and found nothing wrong. An unreachable NMS is a failure to look.
They are both an empty result over the wire, and reporting the second as the first is the most misleading thing this skill can do: it tells an engineer everything is fine at exactly the moment monitoring is blind.
Three outcomes, three different sentences:
| Say | |
|---|---|
| NMS reachable, nothing wrong | "Zabbix reports no active problems as of <time>." |
| NMS unreachable | "Zabbix could not be reached — this is not a statement about the network." |
| Credentials rejected | "Zabbix rejected the credentials — the monitoring state is unknown." |
Acknowledgement is a workflow fact, never a resolution
An acknowledged problem is still happening. Someone has said "I've seen this", which is a fact about the team, not about the network.
Report it as "active, acknowledged by <who> at <when>". Never let acknowledgement soften the description of the underlying condition, and never let a filtered-out acknowledged problem disappear from a count.
Show full SKILL.md (205 more words)Show less
Filtering
Filter before you answer — by severity, host or group — rather than returning everything and asking the
reader to ignore rows. Use severities, hostids or groupids on the call.
Severities: 0 not classified · 1 information · 2 warning · 3 average · 4 high · 5 disaster.
When you filter, say what you filtered out, so "two problems" is never mistaken for "two problems exist".
Resolved problems
event.get with value: 0 gives resolutions. Report both onset and resolution times — a problem that
lasted four minutes and one that lasted four hours are different incidents, and the duration is usually the
point of the question.
Boundaries
| Want to… | Use |
|---|---|
| Metric values over time | zabbix-metrics-history |
| Availability and inventory | zabbix-availability |
| Unsolicited traps | snmptrap-mcp — push, not poll |
| Flows | ipfix-mcp |
| Instrumented metrics / dashboards | prometheus, grafana |
| SaaS monitoring | auvik, thousandeyes, datadog |
| Current device state | pyats, multivendor-cli, fortinet — this is the poller's view over time |
| Acknowledge, close or suppress anything | nothing here. This integration is strictly read-only |
Rules
- Never report an unreachable NMS as "no problems".
- Always give duration, not just onset.
- Acknowledged ≠ resolved. Say "acknowledged", never imply "handled".
- Say what you filtered out.
- Read-only. Acknowledging an alert is a real action a human owns; there is no write path here.
© 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
Files
Just SKILL.md in workspace/skills/zabbix-problem-review of automateyournetwork/netclaw.
Open the folder on GitHubat commit aa90e7d
Compare with similar skills
Zabbix Problem Review 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 Problem Review this skillautomateyournetwork/netclaw | 676 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Is This A Problemanthropics/claude-for-legal | 9.6k | 2 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Relsa Severity AssessmentK-Dense-AI/scientific-agent-skills | 48k | 1 repos | ~5.2k | Automated safety check: Notes | MIT | |
| Reconciling Problem Listsmaziyarpanahi/openmed | 5.5k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Statistical Problem Formulationaiming-lab/AutoResearchClaw | 15k | — | ~671 | Automated safety check: Pass | MIT | |
| Analyze Problemlatitude-dev/latitude-llm | 4.7k | — | ~398 | Automated safety check: Pass | MIT |
Similar skills
- Official
Relsa Severity Assessment
K-Dense-AI/scientific-agent-skills
Supports multivariate severity assessment and exploratory endpoint-time score forecasting for laboratory animal studies using the RELSA (RELative Severity Assessment) score and ARIMA-based foRcast…
Reconciling Problem Lists
maziyarpanahi/openmed
Deduplicate and reconcile OpenMed-extracted conditions into one clean active problem list with clinical status (active / resolved / historical).
Statistical Problem Formulation
aiming-lab/AutoResearchClaw
Formulate statistical research problems with formal notation, target parameters, assumptions, hypotheses, evaluation criteria, and theory targets.
Analyze Problem
latitude-dev/latitude-llm
Analyze a problem and provide a detailed explanation of the issue, root cause, proposed fix, and verification steps.
Boundary Value Problems
parcadei/Continuous-Claude-v3
Problem-solving strategies for boundary value problems in odes pdes
More from automateyournetwork/netclaw
All 120 skills in this repoEVE-NG Lab Topology Design
automateyournetwork/netclaw
Entry point for designing EVE-NG network labs: classifies the request, gathers missing requirements, proposes options and validates the resulting topology.
ACI Policy Change Deployment
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.
Cisco ACI Fabric Health Audit
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.
Anta Validation
automateyournetwork/netclaw
Validate Arista EOS network state against ANTA's pre-built 208-test catalogue, with structured pass/fail verdicts.
Arista Cvp
automateyournetwork/netclaw
Arista CloudVision Portal (CVP) automation via REST API — device inventory, events, connectivity monitoring, tag management (4 tools).
AWS Cloud Monitoring
automateyournetwork/netclaw
AWS CloudWatch monitoring — metrics, alarms, log queries, VPC flow log analysis, network performance.
Questions about Zabbix Problem Review
What does Zabbix Problem Review do?
Review current and historical problems from Zabbix — severity, which host, when it started, how long it has been active, and whether anyone has acknowledged it. Zabbix Problem Review is an agent skill from automateyournetwork/netclaw. Review current and historical problems from Zabbix — severity, which host, when it started, how long it has been active, and whether anyone has acknowledged it.
When should I use Zabbix Problem Review?
Zabbix Problem Review fits situations like: someone asks what is broken right now; how long something has been broken; what happened during a window that has already passed.
How do I install Zabbix Problem Review in Claude Code?
Run `npx skills add automateyournetwork/netclaw --skill zabbix-problem-review -a claude-code`. Or copy the skill folder (workspace/skills/zabbix-problem-review in automateyournetwork/netclaw) into .claude/skills/zabbix-problem-review in your project. Claude Code loads it when a task matches its description.
How do I install Zabbix Problem Review in Codex?
Run `npx skills add automateyournetwork/netclaw --skill zabbix-problem-review -a codex`. Or copy the skill folder (workspace/skills/zabbix-problem-review in automateyournetwork/netclaw) into .agents/skills/zabbix-problem-review in your project. Codex loads it when a task matches its description.
Can I use Zabbix Problem Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add automateyournetwork/netclaw --skill zabbix-problem-review -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-problem-review, .gemini/skills/zabbix-problem-review, .github/skills/zabbix-problem-review and .opencode/skills/zabbix-problem-review in your project.
What does Zabbix Problem Review need to run?
SKILL.md names no scripts, command-line tools or credentials: Zabbix Problem Review is instructions for the agent only. Our summary lists: A credential in ZABBIX_TOKEN.
Does Zabbix Problem Review access the network?
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.
Is Zabbix Problem Review safe to install?
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.
What licence does Zabbix Problem Review use?
Zabbix Problem Review 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.
How many tokens does Zabbix Problem Review use?
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Zabbix Problem Review?
Skills that share tags, products or a category with Zabbix Problem Review: Is This A Problem (anthropics/claude-for-legal, 9.6k stars), Relsa Severity Assessment (K-Dense-AI/scientific-agent-skills, 48k stars), Reconciling Problem Lists (maziyarpanahi/openmed, 5.5k stars) and Statistical Problem Formulation (aiming-lab/AutoResearchClaw, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Zabbix Problem Review?
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 9, 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.