CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

paddle-migrate-lemon-squeezy

Move a Lemon Squeezy integration to Paddle Billing — audit the codebase, inventory the store read-only, map variants to Paddle products and prices, map webhooks and custom data, rebuild license keys, and prepare the subscriber file for a Paddle-assisted migration.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

The canonical home for this skill is paddle-migrate-lemon-squeezy in PaddleHQ/paddle-agent-skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally actionable, well-sequenced migration guide with validation and feedback loops at every stage, held back only by progressive disclosure: everything lives inline in one large SKILL.md rather than being split across bundle files. Moving the two full scripts and the detailed mapping tables into scripts/ and references/ files would complete the picture.

Suggestions

Move the complete lemon-squeezy-inventory.ts and lemon-squeezy-subscriber-file.ts scripts into a scripts/ bundle directory, keeping only their purpose, inputs, outputs, and the rerun/fix loop described inline.

Consider relocating the large variant-mapping and webhook-event mapping tables to a references/ file (e.g. references/mappings.md), leaving a short summary plus pointers in SKILL.md.

Tighten verbose table-cell prose and consolidate the deadline cautions into the single "Read this first" section to reduce token load.

DimensionReasoningScore

Conciseness

The body is dense with task-specific knowledge (field-level mapping tables, API quirks, rate limits, pitfalls) and never explains concepts Claude already knows, assuming competence throughout. A few passages could be trimmed — repeated deadline cautions and verbose explanatory prose inside table cells — and inline time-sensitive dates ("March 31, 2027", "as of November 2026") are not isolated in a dedicated section, so it falls short of the lean anchor 5.

4 / 5

Actionability

The skill provides two complete copy-paste-ready scripts (inventory and subscriber-file generation), a full processEvent webhook handler, SQL DDL, an SDK discount-creation call, an importable ID-map utility, and a runnable grep audit command with a redaction filter. The few app-specific stubs (fulfillment, license key issuance) are explicitly justified placeholders backed by precise event-to-action tables, so the guidance is fully executable for the common cases.

5 / 5

Workflow Clarity

Steps 1–6 are explicitly sequenced with validation checkpoints everywhere: snapshot fields are verified against the API reference before proceeding, the catalog proposal waits for user decisions on flagged rows, unplaceable rows go to needs-fixing.txt with a fix-the-inputs-and-rerun loop, sandbox testing gates the cutover, the cutover itself is strictly ordered ("Only then cancel"), and a post-import reconciliation checklist closes the loop. For a batch migration operation this matches the explicit-validation anchor exactly.

5 / 5

Progressive Disclosure

Sections are well-organized and external references are clearly signaled (Related docs, paired skills, the migration guide URL), but there is no bundle at all: roughly 180 lines of complete scripts are inlined in a ~590-line monolithic SKILL.md — the skill even names their intended scripts/ paths — which matches the anchor of content that should be separate being inline. It is not a 4 because the split into scripts/ files is a substantial, not minor, organization gap.

3 / 5

Total

17

/

20

Passed

Description

82%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 highly specific, action-dense description with strong trigger terms and a distinct niche, whose only weakness is the absence of an explicit "Use when..." trigger clause, which caps completeness at 3. Adding a one-sentence trigger clause would raise it to top marks across all dimensions.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user wants to move an app selling through Lemon Squeezy to Paddle Billing, switch payment processors away from Lemon Squeezy, or prepare a Paddle-assisted store migration."

Optionally include a common synonym such as "switch" or "port" alongside "move"/"migration" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description enumerates six concrete actions spanning the entire migration scope — "audit the codebase, inventory the store read-only, map variants to Paddle products and prices, map webhooks and custom data, rebuild license keys, and prepare the subscriber file" — which matches the comprehensive-coverage anchor; there are no meaningful gaps that would justify a 4.

5 / 5

Completeness

The "what" is clear and comprehensive, but the description contains no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 4 because the 'when' is entirely absent rather than merely implicit-but-stated.

3 / 5

Trigger Term Quality

It contains the exact platform names users would say ("Lemon Squeezy", "Paddle Billing") plus verb synonyms for the core intent ("Move" and "migration"), along with natural domain terms like "license keys", "webhooks", "variants", and "subscriber". Coverage of natural terms including synonyms is comprehensive for this task.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — migrating a Lemon Squeezy integration to Paddle Billing — and the "Lemon Squeezy" qualifier keeps it distinct from generic Paddle setup skills, so it is unlikely to trigger for the wrong skill. Not a 4, since overlap risk with closely related skills is minimal.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (596 lines); consider splitting into references/ and linking

Warning

referenced_paths_exist

Referenced path issues: 3 possibly missing (scripts/lemon-squeezy-inventory.ts, scripts/lemon-squeezy-subscriber-file.ts, scripts/seed-paddle-catalog.ts)

Warning

Total

14

/

16

Passed

Repository

PaddleHQ/paddle-agent-skills

Path

providers/claude/plugin/skills/migrate-lemon-squeezy/SKILL.md

Reviewed

Table of Contents

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.