Name: paddle
Rating: 61.6 (1 reviews)
Author: membranedev

paddle

Paddle integration. Manage Deals, Persons, Organizations, Leads, Projects, Pipelines and more. Use when the user wants to interact with Paddle data.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/paddle/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.

A highly actionable, well-structured CLI integration skill with copy-paste commands and a clear state-machine connection workflow. Its main weaknesses are minor verbosity/promotional prose and a couple of broken cross-references in the step numbering.

Suggestions

Cut the marketing intro ('streamline their payment processes and reduce operational overhead') and deduplicate the `membrane action list --intent=QUERY` command shown in both 'Searching for actions' and 'Popular actions'.

Fix the dangling 'skip to Step 2' reference and the '1b' subheading (there is no 1a) by numbering connect → discover → run as one coherent sequence.

Dimension	Reasoning	Score
Conciseness	The body is largely command-driven and efficient, but it opens with promotional prose ('streamline their payment processes and reduce operational overhead') and repeats the `membrane action list --intent=QUERY` discovery command in two sections, so it could be tightened.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every common case (install, login, connection ensure/get with --wait, action list/run with JSON input, request proxy) plus a concrete flag table, with placeholders clearly explained.	5 / 5
Workflow Clarity	The connection flow has explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop, but it references a 'Step 2' that is never defined and uses a '1b' heading with no '1a', leaving minor gaps.	4 / 5
Progressive Disclosure	No bundle files exist and the content is a single self-contained file organized into clear, navigable sections; it is slightly over the simple-skill line with inline material (proxy flag table, client-action details) that could optionally be split out.	4 / 5
	Total	16 / 20 Passed

Description

70%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.

A solid, mostly explicit description that names the product, lists core entities, and includes a 'Use when' trigger, but it leans on a generic verb and omits natural payment-domain trigger terms. Specificity and the 'when' clause are the main weaknesses.

Suggestions

Replace the generic verb 'Manage' with concrete per-entity actions (e.g., 'create and update Deals, search Persons, list Organizations, manage Pipelines') to raise specificity.

Add natural payment-intent trigger terms — subscriptions, checkout, invoicing, payments, tax compliance — so users describing intent by outcome match this skill.

Dimension	Reasoning	Score
Specificity	It names the Paddle domain and enumerates many concrete entities ('Deals, Persons, Organizations, Leads, Projects, Pipelines') but applies a single generic verb ('Manage') with a vague 'and more', so actions are not distinct or comprehensive.	3 / 5
Completeness	Both 'what' (manage Paddle entities) and 'when' (interact with Paddle data) are explicitly present, but the 'when' clause is somewhat tautological and could name concrete payment intents to reach the top anchor.	4 / 5
Trigger Term Quality	Good keyword coverage of Paddle-specific entity names plus an explicit trigger ('Use when the user wants to interact with Paddle data'), though natural payment-domain synonyms (payments, subscriptions, checkout, invoicing) are missing.	4 / 5
Distinctiveness Conflict Risk	The Paddle branding and 'Paddle data' trigger give it a clear niche with low conflict risk, but the generic CRM-style entity terms (Deals, Persons, Organizations, Leads) create minor overlap with general CRM/data skills.	4 / 5
	Total	15 / 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/paddle/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.