Name: grovo
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

grovo

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

Quality

62%

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

Quality

Content

67%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 a well-structured, actionable CLI integration guide with strong command examples and good validation feedback loops in the connection workflow. Its main weaknesses are mild over-explanation in the intro and a labeling inconsistency around the referenced "Step 2".

Suggestions

Trim the introductory paragraph about what Grovo is and the "auth plumbing" commentary to respect token budget and assume Claude's competence.

Label the action-discovery section explicitly as "Step 2" (or renumber the whole flow) so the "skip to Step 2" reference resolves.

Add a concrete worked example with a real actionId and a sample --input payload, and note result verification for proxy POST/PUT/DELETE calls.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and command-driven, but the intro paragraph explaining what Grovo is ("microlearning platform... train their staff on... software, leadership, and sales") and commentary like "focus on the integration logic rather than auth plumbing" are unnecessary explanation Claude does not need, matching the score-3 anchor; not a 4 because the padding is more than minor.	3 / 5
Actionability	It provides concrete, mostly copy-paste-ready commands (install, login, connection ensure, action list/run, request) plus a flag table, but uses placeholders (CONNECTION_ID, /path/to/endpoint) and gives no concrete actionId example, matching the score-4 anchor; not a 5 because of those minor gaps.	4 / 5
Workflow Clarity	The connection flow has a clear sequence with explicit validation (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR states) and a feedback loop (re-poll after the user completes an action), but the referenced "Step 2" is never explicitly labeled, matching the score-4 anchor; not a 5 because of that labeling gap.	4 / 5
Progressive Disclosure	The single file is well-organized into clear sections (Overview, Install, Authentication, Connecting, Searching, Actions, Proxy, Best practices) with no nesting, but it exceeds 50 lines and has redundancy ("Popular actions" vs "Searching for actions"), matching the score-4 anchor; not a 5 because of the minor redundancy and lack of any reference split.	4 / 5
	Total	15 / 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 clearly answers both what and when and pins a distinct Grovo niche, but its action verbs are generic rather than concrete and its trigger keyword coverage lacks synonyms. Tightening the action list with specific operations and richer trigger terms would lift the specificity and trigger dimensions.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Grovo-specific operations such as "create learning paths, enroll users, and pull completion reports".

Expand the trigger clause with natural synonyms users say, e.g. "Use when the user wants to query Grovo learning data, manage courses, or automate training workflows."

Add file-format or entity keywords (e.g. learning paths, modules, lessons, teams) to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the Grovo domain but its actions ("Manage data, records, and automate workflows") are generic rather than concrete specific operations, matching the score-2 anchor "Names the domain but actions are minimal or generic"; it is not a 3 because it lacks concrete verbs like "extract" or "create".	2 / 5
Completeness	It provides both a "what" ("Grovo integration. Manage data, records, and automate workflows.") and an explicit "when" ("Use when the user wants to interact with Grovo data."), matching the score-4 anchor; not a 5 because the "what" is generic rather than concrete and comprehensive.	4 / 5
Trigger Term Quality	It includes the app name "Grovo" plus relevant terms (data, records, workflows) and an explicit trigger ("interact with Grovo data"), but it misses common variations or synonyms, matching the score-3 anchor; not a 4 because keyword coverage is thin.	3 / 5
Distinctiveness Conflict Risk	The named app "Grovo" with a pinned trigger ("interact with Grovo data") gives a distinct niche, but the generic action verbs (manage data, records, workflows) create minor overlap risk with other data/CRM skills, matching the score-4 anchor; not a 5 because of that residual overlap risk.	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/grovo/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.