Name: crove
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

crove

Crove integration. Manage Organizations, Users, Goals, Filters. Use when the user wants to interact with Crove data.

Quality

68%

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/crove/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 a focused, executable guide to driving Crove through the Membrane CLI with a well-sequenced connection workflow and concrete commands throughout. Its main weaknesses are a brief marketing preamble, an inlined action catalog that could be a reference file, and a few implicit validation steps.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands with little padding, though the opening marketing sentence ("Crove is a document automation platform... saving time and reducing errors") and a few explanatory passages (e.g. the proxy rationale) could be trimmed.	4 / 5
Actionability	It provides concrete, copy-paste-ready commands for installation, auth, connection ensure/poll, action list/run with JSON input, and a proxy flags table; minor gaps remain around filling in CONNECTION_ID and per-action input schemas.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit state handling (BUILDING polling, CLIENT_ACTION_REQUIRED feedback loop, error states) and a retry-after-action checkpoint; only minor validation guidance is implicit rather than enforced.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized with clear section headers and one-level-deep external pointers (official docs URL, --json flags), and no bundle files are present to mis-reference; the large popular-actions table is the one inline block that could live in a separate reference file.	4 / 5
	Total	16 / 20 Passed

Description

62%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 covers both what and when and is anchored to a distinct named app, but it is undermined by a generic verb and an entity list (Organizations, Users, Goals, Filters) that does not reflect the skill's actual document/template capabilities. It reads as templated rather than purpose-built for Crove's real surface area.

Suggestions

Replace the generic "Manage Organizations, Users, Goals, Filters" with the actual capability verbs and entities, e.g. "Create and manage Crove documents and templates, generate PDFs, and send email invitations."

Make the trigger clause concrete: "Use when the user wants to create or update Crove documents, generate PDFs, or send respondent invitations."

Drop vague fluff like "Crove integration." and lead with the specific actions so the description earns every word.

Dimension	Reasoning	Score
Specificity	Names the domain ("Crove integration") and several concrete resource types ("Organizations, Users, Goals, Filters"), but the governing verb "Manage" is generic and the listed entities do not match the skill's actual document/template actions, leaving coverage incomplete.	3 / 5
Completeness	It states both what ("Manage Organizations, Users, Goals, Filters") and when ("Use when the user wants to interact with Crove data"), but the trigger could be more explicit and tied to the real capabilities.	4 / 5
Trigger Term Quality	It includes a single natural trigger clause ("Use when the user wants to interact with Crove data") but "Crove data" is generic and lacks the synonyms or concrete noun phrases (documents, templates, invitations) users would actually say.	3 / 5
Distinctiveness Conflict Risk	Naming the specific app "Crove" gives it a clear niche with minimal conflict risk; slight risk remains because the generic "Manage ... data" phrasing could overlap with other integration skills.	4 / 5
	Total	14 / 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/crove/SKILL.md
Commit: f484c82

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