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

hivebrite

Hivebrite integration. Manage data, records, and automate workflows. Use when the user wants to interact with Hivebrite 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/hivebrite/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 executable CLI commands and a clear, checkpoint-driven connection workflow. Its main weakness is mild verbosity in the overview and a large nested structure list that could be tightened or split out.

Suggestions

Trim the opening platform-description paragraph and collapse the long nested overview tree into a compact list, since Claude can infer Hivebrite's domain from the action discovery flow.

Consider moving the detailed proxy flag table and configuration tree into a short reference section or file so the core workflow stays lean.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands, but the opening paragraph explains what Hivebrite is and the large nested overview list adds padding that could be tightened, fitting the 'mostly efficient with some unnecessary explanation' anchor.	3 / 5
Actionability	Provides concrete, copy-paste-ready `membrane` CLI commands with flags and JSON examples covering install, auth, connection, action discovery, running, and proxying — fully executable guidance for common cases.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-again feedback loop; minor validation gaps keep it just below the top anchor.	4 / 5
Progressive Disclosure	The single file is well-organized into clear sections and no bundle files are needed for this CLI-driven skill, though the large nested overview list is somewhat wall-of-text, leaving minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

66%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 uses third person, names the domain, and includes an explicit 'Use when' trigger giving it solid completeness and distinctiveness. Weaknesses are generic action verbs and limited trigger-term variation, which keep specificity and trigger quality in the mid-range.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Hivebrite actions, e.g. 'manage members, groups, events, and content, and automate workflows'.

Expand trigger terms beyond 'interact with Hivebrite data' to include natural phrases users would say, e.g. 'members, events, groups, posts, or community data in Hivebrite'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Hivebrite') and several actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, matching the anchor that lists 1-2 domain actions without comprehensive coverage.	3 / 5
Completeness	Both 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Hivebrite data') are present; the 'when' is concrete but could be more specific, matching the 4 anchor.	4 / 5
Trigger Term Quality	'interact with Hivebrite data' is a relevant natural phrase, but coverage is thin with no synonyms or variations a user might say, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The named product 'Hivebrite' is a clear niche with a distinct trigger phrase and minimal overlap risk with other skills.	5 / 5
	Total	15 / 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/hivebrite/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.