Name: lemon-squeezy
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

lemon-squeezy

Lemon Squeezy integration. Manage Stores. Use when the user wants to interact with Lemon Squeezy 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/lemon-squeezy/SKILL.md

Quality

Content

82%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 a strong, command-centric integration guide: executable throughout, with a clear connection-state workflow and well-organized sections. Its main gap is the absence of explicit validation/confirmation steps around destructive and batch actions, which prevents a top workflow_clarity score.

Suggestions

Add an explicit validation/confirmation step before destructive actions (e.g. 'Before cancel-subscription or update-customer, retrieve the resource to confirm the target, run the action, then re-retrieve to verify the new state').

Tighten the opening 'Lemon Squeezy is an e-commerce platform...' paragraph or move it after the overview so the skill leads with what the agent must do rather than domain background.

Consider moving the full Popular Actions table into a references file and keeping only the most common actions inline, which would improve progressive disclosure and token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient command-driven reference material that assumes Claude's competence; only minor padding remains (the 'Lemon Squeezy is an e-commerce platform...' intro and a few explanatory sentences about what Membrane does).	4 / 5
Actionability	Provides copy-paste-ready, executable commands for install, login, connection, action search/run, and proxying, plus concrete flag tables and an input-schema example; common cases are fully covered.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with explicit state checks (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a polling loop, but destructive actions (cancel-subscription, update-customer) lack an explicit validate/confirm-then-retry checkpoint.	4 / 5
Progressive Disclosure	Well-organized into logical sections with the action catalog usefully inlined as a table and no nested/external references; slightly dense for a single SKILL.md but appropriately structured given no bundle files exist.	4 / 5
	Total	17 / 20 Passed

Description

48%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 names a distinct niche and includes a 'Use when' trigger, but it is vague about capabilities ('Manage Stores') and lacks the concrete trigger phrases (subscriptions, orders, license keys) that would make it reliably invocable. It reads more like a tagline than a capability spec.

Suggestions

List concrete actions in the description, e.g. 'List and retrieve products, variants, orders, subscriptions, customers, and license keys; create checkouts and customers; cancel subscriptions.'

Expand the 'Use when' clause with natural trigger phrases a user would say, such as 'when the user wants to manage Lemon Squeezy subscriptions, orders, license keys, checkouts, or customer data'.

Replace the terse 'Manage Stores.' with verbs that match the actual API surface so the description reflects what the skill can really do.

Dimension	Reasoning	Score
Specificity	Names the domain ('Lemon Squeezy integration') and only one minimal, generic action ('Manage Stores'), with no enumeration of the concrete operations visible in the skill (list/create/update/cancel on products, orders, subscriptions, etc.).	2 / 5
Completeness	It has a clear 'what' (Lemon Squeezy integration / manage stores) and an explicit 'Use when...' clause, but the 'when' is generic ('interact with Lemon Squeezy data') rather than tied to concrete trigger phrases, and the 'what' is thin.	3 / 5
Trigger Term Quality	'interact with Lemon Squeezy data' is a reasonable natural trigger, but it omits common synonyms and concrete nouns a user would say (subscriptions, payments, orders, license keys, checkouts).	3 / 5
Distinctiveness Conflict Risk	The Lemon Squeezy brand is a clear niche with minimal conflict risk against other skills; only minor overlap risk with a generic e-commerce/payments skill.	4 / 5
	Total	12 / 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/lemon-squeezy/SKILL.md
Commit: f484c82

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