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 whose code, commands, and mapping tables are directly executable and whose batch operations are guarded by real validation loops. Its weaknesses are structural: everything is inlined in one very long SKILL.md with no bundle files, and a few guidance points are stated more than once.

Suggestions

Move the two full TypeScript scripts (lemon-squeezy-inventory.ts, lemon-squeezy-subscriber-file.ts) into a scripts/ directory and keep only run instructions and input/output contracts inline.

Split the webhook event-mapping and catalog-mapping tables into a references/ file, surfacing only the flagged/exception rows inline at the point of use.

De-duplicate guidance repeated across "Read this first", Step 6, "Cut over", and "Common pitfalls" (cancellation timing, card_brand grouping) into a single canonical location.

DimensionReasoningScore

Conciseness

The prose is dense and migration-specific with virtually no explanation of concepts Claude already knows, but a few points are repeated across sections (cancellation timing in Lemon Squeezy appears in "Read this first", "Cut over", and "Common pitfalls"; the card_brand/payment_processor grouping appears in both Step 6 and the pitfalls), so minor trimming is possible. It is not 5 given these repeats and the overall 59KB size, and not 3 since nearly every sentence carries non-derivable, task-specific facts.

4 / 5

Actionability

The body provides copy-paste-ready material throughout: an exact grep/sed audit command, two complete executable TypeScript scripts, SQL DDL, a full webhook handler with SDK imports, and precise env-var and API-permission lists. The two stubbed handler branches are explicitly justified app-specific fulfillment, not pseudocode gaps.

5 / 5

Workflow Clarity

Steps 1–6 plus "Cut over" and "Verify the integration" give a clear, ordered sequence with explicit validation checkpoints and feedback loops: field-checking the snapshot against the API reference, "Report the three counts and show needs-fixing.txt ... then fix the inputs and rerun", confirming Paddle IDs before writing the map, sandbox testing, and post-import reconciliation — exactly the validation the batch subscriber-file operation requires.

5 / 5

Progressive Disclosure

There are no bundle files (references/, scripts/, assets/ all absent), so all ~590 lines live inline in SKILL.md, including two full scripts already labeled with scripts/ path comments and large webhook/catalog mapping tables that clearly belong in separate files. Section structure is good, but content that should be separate is inline — more than the "minor organization gaps" of score 4.

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, distinctive description that enumerates the full set of concrete migration actions. Its only material weakness is the absence of an explicit 'Use when...' trigger clause, leaving the invocation condition implied rather than stated.

Suggestions

Append an explicit trigger clause, e.g. "Use when an app sells through Lemon Squeezy and the user wants to move billing to Paddle."

Include a common user phrasing variation such as "switching off Lemon Squeezy" or "Lemon Squeezy shutdown" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description lists six distinct concrete actions — "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" — giving comprehensive coverage of the migration workflow, matching the score-5 anchor of multiple specific concrete actions.

5 / 5

Completeness

The "what" is clearly and concretely answered, but there is no "Use when..." clause or equivalent explicit trigger guidance; the "when" is only weakly implied by the opening phrase "Move a Lemon Squeezy integration to Paddle Billing", which the judging guidelines cap at 3.

3 / 5

Trigger Term Quality

The natural phrases a user would say are all present: "Lemon Squeezy", "Paddle Billing", "Move ... to", plus domain nouns (variants, webhooks, custom data, license keys, subscriber file). For a platform-to-platform migration the two platform names are the decisive triggers and both appear, so no meaningful synonym is missing.

5 / 5

Distinctiveness Conflict Risk

Naming both the source platform (Lemon Squeezy) and the target (Paddle Billing) carves out a clear niche with distinct triggers, so the risk of firing for the wrong payment-provider skill 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/codex/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.