Name: zenhub
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

zenhub

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

Quality

70%

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/zenhub/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 body is highly actionable with copy-paste-ready Membrane commands and a sound connect-and-poll workflow, slightly let down by minor over-explanation and an unnumbered step sequence rather than by structure.

Dimension	Reasoning	Score
Conciseness	The body is largely lean concrete commands with brief context, but the opening ZenHub intro paragraph and phrases like "so you can focus on the integration logic rather than auth plumbing" are minor over-explanation that could be trimmed.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands covering the common cases: CLI install, login, connection ensure, action list/run, and proxy requests, each with the relevant flags and --json output.	5 / 5
Workflow Clarity	There is a clear install → authenticate → connect → poll-until-ready → search → run sequence with a real polling feedback loop for CLIENT_ACTION_REQUIRED, but the loose "Step 2" and "1b" references without a numbered Step 1 leave minor sequence gaps.	4 / 5
Progressive Disclosure	Content is well organized into clearly headed sections (Overview, Working with ZenHub, Searching, Popular actions, Proxy, Best practices) with no broken references; since no bundle files exist everything is inline, which is reasonable for this size but the proxy-options and connection-state details could live in a reference file.	4 / 5
	Total	17 / 20 Passed

Description

57%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 correctly answers both what and when and is anchored to a distinct brand, but its action list is generic rather than ZenHub-specific and its trigger terms are limited to the product name alone.

Suggestions

Replace generic actions with concrete ZenHub capabilities, e.g. "move issues across pipelines, set estimates, manage dependencies, and view burndown charts".

Expand the trigger clause with natural terms users say, e.g. "Use when working with ZenHub workspaces, pipelines, sprints, epics, estimates, or burndown charts".

Tighten "Manage data, records, and automate workflows" which reads as filler and weakens specificity.

Dimension	Reasoning	Score
Specificity	The description names the ZenHub domain but the actions "Manage data, records, and automate workflows" are generic verbs on generic nouns rather than concrete ZenHub-specific actions (e.g. moving issues between pipelines, setting estimates, viewing burndown charts).	2 / 5
Completeness	Both "what" (ZenHub integration, manage data/records/workflows) and an explicit "when" ("Use when the user wants to interact with ZenHub data") are present, though the when clause is generic and could be more specific.	4 / 5
Trigger Term Quality	The trigger relies on the single brand keyword "ZenHub" / "ZenHub data"; it lacks the natural variations and synonyms users would say such as sprints, epics, pipelines, or burndown.	3 / 5
Distinctiveness Conflict Risk	The ZenHub brand name gives the skill a clear, distinct niche with minimal conflict risk, but the generic "manage data, records, and automate workflows" phrasing introduces minor overlap with other integration skills.	4 / 5
	Total	13 / 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/zenhub/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.