zabbix

Read Zabbix monitoring state to produce incident triage summaries.

126|11|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/HybridAIOne/hybridclaw --skill zabbix-hybridaione
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zabbix
Source: https://github.com/HybridAIOne/hybridclaw/tree/main/skills/zabbix
Command: npx skills add https://github.com/HybridAIOne/hybridclaw --skill zabbix-hybridaione

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Zabbix monitoring outputs raw alert and problem data that teams need to quickly interpret into actionable incident context without risking credential exposure.

Core Features & Use Cases

  • Read-only Zabbix incident context: Retrieves API health, monitored host inventory, current and recent problems, and trigger problems by severity for triage workflows.
  • Guarded incident-response summaries: Produces concise summaries that include key identifiers and state (acknowledged/suppressed, age, tags, severity) so other maintenance skills can investigate and remediate.
  • Safe credential handling: Uses a stored bearer token and builds gateway-proxied http_request payloads without printing Authorization headers or token values.

Quick Start

Ask HybridClaw to read Zabbix problems and produce a concise incident triage summary for the most recent events using the zabbix monitoring reads skill.

Frequently Asked Questions about zabbix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage Zabbix incidents without exposing API credentials?

Triage Zabbix incidents safely by using a stored bearer token to build gateway-proxied http_request payloads. This method retrieves monitoring state and problem context for incident triage without printing Authorization headers or exposing Zabbix credentials.

What Zabbix problem data can I filter by when querying recent alerts?

Query Zabbix problem data by filtering results across severity, acknowledgment state, suppression state, tags, and time windows. This filtering capability yields precise incident triage context for production operations scenarios.

Can I acknowledge or suppress Zabbix alerts through this monitoring read method?

No, you cannot acknowledge, suppress, close, update, or delete Zabbix alerts. The method strictly enforces read-only JSON-RPC calls to retrieve host inventory and trigger problems, preventing guarded operations that modify Zabbix state.

How do I prepare the Zabbix frontend URL for JSON-RPC API calls?

Validate the Zabbix frontend URL by normalizing it to point directly to the JSON-RPC endpoint before making authenticated calls. This validation ensures gateway-proxied http_request payloads reach the correct API interface for read-only monitoring queries.

What information is included in a Zabbix incident triage summary?

Zabbix incident triage summaries include key problem identifiers and current state details such as acknowledgment status, suppression state, age, tags, and severity. This concise output helps other maintenance skills investigate and remediate production issues.

Do I need a specific token type to authenticate Zabbix API monitoring reads?

Yes, you need a stored ZABBIX_API_TOKEN bearer secret to authenticate Zabbix monitoring calls. The token authorizes gateway-proxied http_request payloads to retrieve host inventory and trigger problem data without credential exposure.