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

Blog Docs Log in Get started

clover

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

Quality

63%

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

Quality

Content

68%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 commands and a solid connection-state workflow, but it is held back by mild over-explanation up front and a destructive-proxy path lacking verification guidance plus an undefined 'Step 2' reference.

Suggestions

Trim the 'Clover is a POS system...' intro and the unexplained Clover Overview entity list, or replace them with a one-line pointer to Clover's domain model that the agent actually needs.

Add a verification/retry step for destructive proxy calls (e.g. GET the resource after a PUT/DELETE to confirm, and check the response status before proceeding).

Define the referenced 'Step 2' (what to do once the connection is READY) so the 'skip to Step 2' instruction resolves to a concrete section.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command documentation, but the opening 'Clover is a point-of-sale (POS) system...' paragraph and the unexplained 'Clover Overview' entity list (Meeting/Contact/Account/Opportunity/Lead) are unnecessary explanation Claude largely already knows or that adds little, fitting the 'mostly efficient with some unnecessary explanation' anchor rather than the tighter 4.	3 / 5
Actionability	It provides copy-paste-ready commands for every phase (install, login, connection ensure, action list/run with --input JSON, request) plus a complete proxy flag table, covering the common cases fully and earning the 5 anchor.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with state-based polling checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the proxy path supports destructive methods (DELETE/PUT) with no verification step, and 'Step 2' is referenced but never defined, capping it at 3 per the destructive-operation guideline.	3 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is organized into clear, well-signaled sections (Auth, Connecting, Searching, Running, Proxy, Best practices) with no nested references, giving good structure with only minor organization gaps rather than the ideal 5.	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 correctly pairs a 'what' with an explicit 'Use when' trigger and leverages a distinct brand name, but its capability list is generic and its trigger terms lack the natural POS/payment vocabulary users would actually say.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Clover capabilities such as 'query orders, process payments, manage inventory, and pull merchant records'.

Broaden trigger terms to include natural phrasings like 'Clover POS', 'Clover payments', 'Clover orders', or 'Clover merchant data' so the skill surfaces for real user requests.

Tighten the 'when' clause to the POS/payments context, e.g. 'Use when the user wants to query or manage Clover POS data — orders, payments, inventory, or merchant records.'

Dimension	Reasoning	Score
Specificity	It names the Clover domain but the listed actions — 'Manage data, records, and automate workflows' — are minimal and generic rather than concrete capabilities; it does not reach the 1-2 specific actions of anchor 3.	2 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Clover data'), but the 'when' could be more specific about POS/payments contexts rather than the generic 5 anchor.	4 / 5
Trigger Term Quality	It includes relevant terms ('Clover', 'Clover data') and an explicit trigger phrase, but misses common natural variations users would say such as 'Clover POS', 'Clover payments', 'orders', or 'inventory', fitting the 'some keywords but missing synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	'Clover' is a distinct named POS brand giving it a clear niche and low conflict risk, but the generic 'data, records, workflows' framing leaves minor overlap risk with other integration skills, keeping it just below 5.	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/clover/SKILL.md
Commit: f484c82

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