Name: groovehq
Rating: 63.2 (1 reviews)
Author: membranedev

groovehq

GrooveHQ integration. Manage Tickets, Customers, Users, Groups, Labels, Reports. Use when the user wants to interact with GrooveHQ data.

Quality

75%

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

Quality

Content

71%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 concrete, executable CLI commands and a strong connection-state workflow. It is held back by an unnecessary intro explanation and an inlined actions table that would benefit from separation into a reference file.

Suggestions

Remove or trim the introductory paragraph explaining what GrooveHQ is and the thin 'GrooveHQ Overview' list, since Claude already knows the product context.

Move the 'Popular actions' table into a separate references file (e.g. ACTIONS.md) and link to it from the body to improve progressive disclosure.

Unify the connection, action-search, and action-run sections into a single numbered end-to-end workflow so the full sequence is explicit.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with direct commands, but the intro paragraph explaining what GrooveHQ is ('help desk software designed for small businesses...') and the thin 'GrooveHQ Overview' list are unnecessary padding Claude does not need.	3 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request proxy) with a complete flag-options table and JSON examples covering the common cases.	5 / 5
Workflow Clarity	The connection sub-flow is clearly sequenced with explicit state-based validation checkpoints and a re-auth feedback loop, but the overall end-to-end sequence (connection -> search -> run) is not unified into a single numbered workflow.	4 / 5
Progressive Disclosure	Good section structure exists, but no bundle/reference files are used and the large 'Popular actions' table is inlined reference-bulk content that would be better split into a separate file.	3 / 5
	Total	15 / 20 Passed

Description

78%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 clear, third-person, and covers both capabilities and an explicit use-trigger, anchored to a well-defined product niche. Its main weakness is the generic single-verb action framing and a somewhat vague 'when' clause.

Dimension	Reasoning	Score
Specificity	Lists several specific managed entities ('Tickets, Customers, Users, Groups, Labels, Reports'), but a single generic verb ('Manage') governs them rather than multiple distinct concrete actions, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both 'what' (manage the listed entities) and 'when' ('Use when the user wants to interact with GrooveHQ data'), but the 'when' clause is generic rather than a concrete trigger phrase, so it falls short of the 5 anchor.	4 / 5
Trigger Term Quality	Good keyword coverage of the domain ('GrooveHQ', 'Tickets, Customers, Users, Groups, Labels, Reports'), though the trigger clause is a single generic phrase ('interact with GrooveHQ data') missing natural synonym variations.	4 / 5
Distinctiveness Conflict Risk	'GrooveHQ' is a clearly named niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 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/groovehq/SKILL.md
Commit: f484c82

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