Name: upserve
Rating: 56.8 (1 reviews)
Author: membranedev

upserve

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

Quality

65%

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/upserve/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 body is highly actionable with executable Membrane CLI commands and a solid connection workflow, but it loses conciseness to a low-value entity list and leaves the destructive proxy operations without validation checkpoints.

Suggestions

Add a verify step for mutating proxy/action calls (e.g. confirm via a GET or check the response state) so destructive operations have a feedback loop.

Trim or annotate the 45-item entity list — either group it into categories with one-line purposes or move it to a reference file.

Fix the dangling "skip to Step 2" reference by labeling the target section (e.g. "## Step 2: Run actions") or rephrasing the pointer.

Dimension	Reasoning	Score
Conciseness	Command examples are lean and earn their tokens, but the ~45-item undifferentiated entity list ("Shift", "Tip", ... "Training Material") with no usage guidance, plus redundancy between "Searching for actions" and "Popular actions", adds padding that could be trimmed.	3 / 5
Actionability	Copy-paste-ready commands cover the common cases end to end — install, login, connection ensure/get, action list/run with JSON input, and proxy requests with a full flag table — giving Claude exactly what to execute.	5 / 5
Workflow Clarity	The connection flow has an explicit state-machine sequence with checkpoints and a poll-after-action feedback loop, but the destructive proxy path (POST/PUT/PATCH/DELETE) has no validation/verification steps and the "skip to Step 2" reference points to a step that is never labeled, leaving validation gaps that cap this dimension.	3 / 5
Progressive Disclosure	A single self-contained file with clear section headers and no external references needed for a CLI skill; minor organization gaps include the redundant "Popular actions" section and the long unannotated entity wall.	4 / 5
	Total	15 / 20 Passed

Description

61%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 clearly scoped to Upserve and includes an explicit Use-when trigger, but its capability list is generic ("manage data, records, automate workflows") rather than naming concrete Upserve actions, which weakens specificity and trigger richness.

Suggestions

Replace generic verbs with concrete Upserve actions, e.g. "Pull sales and payment reports, manage menu items and checks, and look up reservations and guest data."

Broaden trigger terms to natural phrases users say, such as "Upserve POS", "restaurant sales reports", or "Upserve reservations".

Tighten the what/when pairing so the capabilities named in the "what" directly mirror the scenarios in the "when" clause.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Upserve integration") but its actions are minimal and generic — "Manage data, records, and automate workflows" offers no concrete operations, and "manage data"/"manage records" are near-synonymous abstractions rather than distinct capabilities.	2 / 5
Completeness	Both halves are present — a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Upserve data") — but the "what" is generic and the trigger could name more concrete Upserve scenarios.	4 / 5
Trigger Term Quality	"Upserve" and "interact with Upserve data" are the relevant natural keywords a user would say, but coverage stops at the single product name with no common variations or synonyms (e.g. restaurant POS, Upserve POS, analytics).	3 / 5
Distinctiveness Conflict Risk	Tied to a single named product ("Upserve") with product-specific triggers ("interact with Upserve data"), it occupies a clear niche with minimal overlap risk against other skills.	5 / 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/upserve/SKILL.md
Commit: f484c82

Reviewed: 3 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.