Name: logz-io
Rating: 59.2 (1 reviews)
Author: membranedev

logz-io

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

Quality

68%

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/logz-io/SKILL.md

Quality

Content

75%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 content is highly actionable with concrete, executable Membrane CLI commands and a well-structured state-driven connection workflow that includes polling and feedback loops. Its weaknesses are an explanatory opening paragraph that tells Claude things it already knows and slightly inconsistent step numbering that could confuse navigation.

Suggestions

Cut the opening "Logz.io is a cloud-based..." paragraph or compress it to one line so the skill does not spend tokens restating what Claude already knows.

Fix the step numbering (add a "1a"/renumber sections and clearly mark the referenced "Step 2") so the connection workflow is unambiguous to follow.

Consider moving the verbose clientAction field reference and the proxy flags table into a reference file linked from the body to tighten the overview and strengthen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight commands, but opens by explaining what Logz.io is ("Logz.io is a cloud-based log management and observability platform...") and pads the Membrane auth explanation, matching the anchor for mostly-efficient content with some unnecessary explanation Claude already knows.	3 / 5
Actionability	Commands are fully executable and copy-paste ready across the common cases (install, login, connection ensure, action list/run, request proxy) with concrete flags and a parameter table, matching the level-5 anchor for fully executable guidance covering common cases.	5 / 5
Workflow Clarity	The connection workflow has a clear state-driven sequence with feedback loops (poll with --wait, branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after action), but the numbering is inconsistent (a "1b" with no "1a", an orphan "Step 2" reference), fitting the anchor for a clear sequence with minor gaps.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clear sections with no external references (and none are bundled), so content is appropriately placed; at ~145 lines it exceeds the simple-skill exception, and the long clientAction spec and proxy flag table could be split out, matching the good-structure-with-minor-gaps anchor.	4 / 5
	Total	16 / 20 Passed

Description

62%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 is in third person and successfully pairs a what-clause with an explicit "Use when" trigger, avoiding the cap that applies when triggers are missing. Its main weakness is generic action language ("manage data, records") and thin natural-keyword coverage beyond the product name itself.

Suggestions

Replace generic verbs with concrete Logz.io capabilities, e.g. "Query logs, create alerts, build dashboards, and archive records in Logz.io. Use when the user wants to work with Logz.io logs, alerts, metrics, traces, or dashboards."

Add natural synonyms and entities users actually mention (logs, alerts, dashboards, metrics, traces) to broaden trigger-term coverage.

Tie the "when" clause to specific artifacts (e.g. "when the user mentions Logz.io alerts, dashboards, or log searches") to sharpen the trigger.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Logz.io domain plus 2-3 actions, but the actions are generic ("data", "records") rather than concrete like "extract logs" or "create alerts", fitting the anchor for naming a domain with 1-2 actions but not comprehensive coverage.	3 / 5
Completeness	It has both a clear "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Logz.io data"), but the "what" is generic rather than concrete, so it fits the anchor for having both with room for more specificity rather than the comprehensive level-5 example.	4 / 5
Trigger Term Quality	"Logz.io" and "data" are the only natural keywords; common variations, synonyms, or related terms users might say (logs, alerts, dashboards, metrics) are absent, matching the anchor for some relevant keywords but missing common variations.	3 / 5
Distinctiveness Conflict Risk	The named product "Logz.io" gives a clear niche with minimal conflict risk, but the action phrasing is generic enough to leave minor overlap risk with other observability/integration skills, matching the "mostly distinct, minor overlap risk" anchor.	4 / 5
	Total	14 / 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/logz-io/SKILL.md
Commit: f484c82

Reviewed: 6 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.