Name: zuplo
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

zuplo

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

Quality

66%

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/zuplo/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 body is highly actionable with concrete CLI commands and a well-structured, validated connection workflow, but it carries some marketing fluff and inconsistent step labeling that prevent a top score. It appropriately keeps everything inline given the absence of bundle files.

Suggestions

Trim the marketing intro ('Think of it as a reverse proxy with superpowers for API management') to a one-line factual description of Zuplo.

Fix the step numbering: label the initial connect step as Step 1a/Step 1 and define the referenced 'Step 2' (searching/running actions) explicitly so 'skip to Step 2' resolves.

Consider splitting the connection-state reference (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR field details) into a references file to reduce inline length now that the skill exceeds 50 lines.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the marketing-style intro ('Think of it as a reverse proxy with superpowers for API management') and phrasing like 'so you can focus on the integration logic rather than auth plumbing' add unnecessary padding, fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides copy-paste-ready executable commands throughout (install, login, connection ensure, action run, request) plus a concrete flags table, fully covering the common cases as the level-5 anchor requires.	5 / 5
Workflow Clarity	The connect-to-run flow is clearly sequenced with validation checkpoints (polling until state leaves BUILDING, handling CLIENT_ACTION_REQUIRED, checking the error field), but 'skip to Step 2' references an unlabeled step and the 1b/Step-2 numbering is inconsistent, fitting 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	No bundle files exist, so all content is inline, but it is well-organized into clearly headed sections (Overview, Install, Authentication, Connecting, Searching, Actions, Proxy, Best practices) with no nested references, matching 'good structure; most content appropriately placed; minor organization gaps'.	4 / 5
	Total	16 / 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 successfully pairs a what-statement with an explicit 'Use when' trigger and leverages a distinctive product name, but its action list is generic rather than reflecting Zuplo's specific API-gateway features. Tightening the actions and adding more concrete trigger terms would lift the weaker dimensions.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with Zuplo-specific capabilities such as managing routes, environments, secrets, and custom domains.

Expand the trigger clause to mention natural phrases users would say, e.g. 'Use when the user wants to manage Zuplo API routes, environments, secrets, or custom domains.'

Mention file extensions or product-specific terms (e.g. 'Zuplo project', 'Zuplo API key') to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the domain (Zuplo) but its actions ('Manage data, records, and automate workflows') are generic and not tied to Zuplo's concrete API-gateway capabilities, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It states both what it does ('Manage data, records, and automate workflows') and an explicit when ('Use when the user wants to interact with Zuplo data'), but the when could be more specific about Zuplo use cases, matching the 'has both what and when; when could be more explicit' anchor rather than the fully concrete level 5.	4 / 5
Trigger Term Quality	The phrase 'Use when the user wants to interact with Zuplo data' surfaces the natural keyword 'Zuplo', but it lacks common variations or synonyms (e.g. API gateway, routes, proxies), fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Zuplo' is a distinct named product so the trigger is unlikely to fire for unrelated skills, though the generic 'manage data, records' phrasing leaves minor overlap risk, fitting 'mostly distinct; minor overlap risk' rather than the minimal-risk level 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/zuplo/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.