Name: ezeep-blue
Rating: 64.8 (1 reviews)
Author: membranedev

ezeep-blue

Ezeep Blue integration. Manage Users, Organizations, Printers. Use when the user wants to interact with Ezeep Blue data.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ezeep-blue/SKILL.md

Quality

Content

82%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 copy-paste CLI commands and a clear connection workflow featuring explicit state-based feedback loops. Weaker spots are minor over-explanation in the intro and the absence of validation guidance for destructive data operations.

Suggestions

Add a validation/confirmation step before running destructive actions (e.g., 'Confirm with the user before deleting a user or removing a printer').

Trim the introductory 'Ezeep Blue is a print management solution...' paragraph since the description already conveys the product's purpose.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with dense, copy-paste CLI commands, but the introductory paragraph ('Ezeep Blue is a print management solution...') and a few explanatory asides ('so you can focus on the integration logic rather than auth plumbing') could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready commands are provided throughout (install, login, connection ensure/get, action list/run, request) plus a popular-actions table with keys, covering the common cases concretely.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state checkpoints and feedback loops (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll), but the action-execution flow lacks validation guidance for potentially destructive operations like user/printer management.	4 / 5
Progressive Disclosure	No bundle files exist and the skill is self-contained with well-organized sections (Overview, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices); minor gaps like the proxy-flags table being fully inline rather than referenced keep it from a 5.	4 / 5
	Total	17 / 20 Passed

Description

73%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 third-person, names a distinct product, and includes an explicit 'Use when' clause covering both what and when. Its main weakness is the generic verb 'Manage' and a trigger clause that could enumerate concrete phrases like 'print jobs' or 'printing'.

Suggestions

Replace the single verb 'Manage' with distinct concrete actions (e.g., 'List and create users, manage organizations, submit and monitor print jobs').

Tighten the trigger clause with concrete phrases: 'Use when the user wants to manage printers, print jobs, users, or organizations in Ezeep Blue.'

Dimension	Reasoning	Score
Specificity	Names the domain ('Ezeep Blue integration') and lists entities ('Manage Users, Organizations, Printers'), but the single generic verb 'Manage' applied to three entities is not the multiple distinct concrete actions a score of 4 requires.	3 / 5
Completeness	Both 'what' ('Manage Users, Organizations, Printers') and an explicit 'when' ('Use when the user wants to interact with Ezeep Blue data') are present, but the trigger clause is generic rather than enumerating concrete trigger phrases, matching the anchor 4 example.	4 / 5
Trigger Term Quality	Natural terms a user would say are present ('Ezeep Blue', 'Printers', 'Users', 'Organizations', 'interact with Ezeep Blue data'); common variations like 'print jobs' or 'printing' are missing, keeping it just short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	'Ezeep Blue integration' names a specific product with a clear niche and distinct triggers, presenting minimal conflict risk with other skills.	5 / 5
	Total	16 / 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/ezeep-blue/SKILL.md
Commit: f484c82

Reviewed: ~21 hours 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.