Name: hive
Rating: 68 (1 reviews)
Author: membranedev

hive

Hive integration. Manage Users, Projects, Actions, Notes, Files, Activities and more. Use when the user wants to interact with Hive data.

Quality

83%

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

Quality

Content

78%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 CLI commands and a clear connection workflow with validation checkpoints. Its main weaknesses are an inlined reference table that should live in a separate file and minor conciseness and step-numbering gaps.

Suggestions

Move the 20-row "Popular actions" table into a separate references file (e.g., ACTIONS.md) and link to it from the body, keeping only a few key examples inline.

Fix the step numbering/headers so the "skip to Step 2" and "1b" references resolve to actual labeled steps.

Trim explanatory prose like "so you can focus on the integration logic rather than auth plumbing" and the opening Hive-marketing paragraph to reduce token cost.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste CLI commands and tables, but includes mild over-explanation such as "so you can focus on the integration logic rather than auth plumbing" and a background paragraph on what Hive is that could be trimmed.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) with flags and JSON input examples covering the common cases.	5 / 5
Workflow Clarity	The connect-to-run sequence is clearly laid out with explicit state-based checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a polling feedback loop, but the numbering is inconsistent ("skip to Step 2" with no Step 2 header, "1b" without a "1a").	4 / 5
Progressive Disclosure	Sections are reasonably organized, but a large inline "Popular actions" reference table (20 rows) and the proxy-options table are content that would be better split into a separate reference file; there are no external references at all to offload detail.	3 / 5
	Total	16 / 20 Passed

Description

87%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 concise, concrete, and clearly identifies both the capability and the trigger condition for a specific platform. Its only weakness is the open-ended "and more" and slightly limited natural-phrase coverage.

Suggestions

Replace "and more" with one or two additional concrete managed entities (e.g., "Workspaces, Portfolios") to close the coverage gap.

Add a couple of natural user phrasings or file/intent terms (e.g., "Hive tasks", "Hive projects") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and several concrete managed entities ("Manage Users, Projects, Actions, Notes, Files, Activities and more"), listing several specific actions with only minor coverage gaps implied by "and more".	4 / 5
Completeness	It explicitly states what the skill does ("Manage Users, Projects, Actions, Notes, Files, Activities") and gives an explicit trigger clause ("Use when the user wants to interact with Hive data"), answering both what and when clearly.	5 / 5
Trigger Term Quality	It includes the natural product term "Hive" and the natural phrase "interact with Hive data", giving good keyword coverage, though a few common phrasings users might say are not enumerated.	4 / 5
Distinctiveness Conflict Risk	Tied to a named platform ("Hive integration") with distinct triggers ("interact with Hive data"), it occupies a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	18 / 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/hive/SKILL.md
Commit: f484c82

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