Name: zabbix
Rating: 51.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

zabbix

Zabbix integration. Manage data, records, and automate workflows. Use when the user wants to interact with Zabbix data.

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/zabbix/SKILL.md

Quality

Content

63%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers concrete, executable Membrane CLI commands and a well-sequenced connection workflow with state checkpoints, but it opens with unnecessary background on what Zabbix is and inlines reference-style detail (flags tables, schema fields) that would benefit from being split into separate, clearly-signaled files. Trimming the boilerplate and extracting reference material into linked files would improve conciseness and progressive disclosure.

Suggestions

Remove the opening 'Zabbix is an open-source monitoring solution...' paragraph and similar explanatory filler that Claude already knows.

Extract the proxy flags table and action inputSchema/outputSchema reference into a separate REFERENCE.md linked from the body to improve progressive disclosure.

Add an explicit output-validation step after `membrane action run` (e.g. check the `output` field for errors) to close the workflow feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command-first documentation, but it includes unnecessary filler Claude already knows (the opening 'Zabbix is an open-source monitoring solution for networks, servers, VMs...' paragraph and the explanatory 'Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing'), so it is mostly efficient with some sections that could be tightened.	3 / 5
Actionability	It provides concrete, copy-pasteable CLI commands for install, login, connection, action search/run, and proxy requests with a flags table, giving mostly executable guidance with only minor gaps (e.g. placeholder CONNECTION_ID is used but never tied to an example value).	4 / 5
Workflow Clarity	The connection flow is clearly sequenced (ensure -> poll state -> handle CLIENT_ACTION_REQUIRED -> READY -> search actions -> run) with explicit polling/state checkpoints and error states, yielding a clear sequence with most checkpoints present; only the final action-execution loop lacks an explicit verify-output checkpoint.	4 / 5
Progressive Disclosure	Content is organized into reasonable sections, but there are no bundle/reference files and no external one-level-deep links — substantial reference-style material (the proxy flags table, action schemas, state-handling detail) is inlined in SKILL.md rather than split into separate referenced files, matching the 'Some structure but content that should be separate is inline' anchor.	3 / 5
	Total	14 / 20 Passed

Description

50%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly names the Zabbix niche and includes an explicit Use-when clause, but its actions are generic ('Manage data, records, and automate workflows') and it omits the natural Zabbix vocabulary users would actually say (hosts, items, problems, alerts, monitoring). Tightening the action list and adding domain trigger terms would raise specificity and trigger-term quality.

Suggestions

Replace generic verbs with concrete Zabbix capabilities, e.g. 'Query hosts, items, and problems; acknowledge alerts; manage triggers and templates.'

Add natural trigger terms users say, such as 'monitoring', 'alerts', 'hosts', 'items', 'problems', or 'triggers'.

Sharpen the 'Use when' clause to specific intents, e.g. 'Use when the user wants to query Zabbix monitoring data or acknowledge/manage problems.'

Dimension	Reasoning	Score
Specificity	The description names the Zabbix domain and the verbs 'Manage data, records, and automate workflows', but these actions are generic and minimal — 'records' is vague jargon and the actions map to no concrete Zabbix capabilities, matching the 'Names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It states a clear 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Zabbix data'), satisfying both, though the 'when' could be more specific than the generic 'interact with Zabbix data'.	4 / 5
Trigger Term Quality	The only natural term is 'Zabbix' plus the generic 'data' and 'workflows'; common user phrasings such as 'hosts', 'items', 'problems', 'alerts', or 'monitoring' are absent, so it has one or two generic keywords missing the natural phrases users say.	2 / 5
Distinctiveness Conflict Risk	'Zabbix integration' is a clear niche with a named product trigger, giving it mostly distinct triggers with only minor overlap risk against other generic data-management skills.	4 / 5
	Total	12 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/zabbix/SKILL.md
Commit: f484c82

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.