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

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.

The body is an exceptionally actionable, well-sequenced migration runbook: complete scripts, precise mapping tables, decision gates, and validation feedback loops at every fragile stage. Its weaknesses are structural — a fully inlined ~590-line file with no scripts/ or references/ split despite naming script paths in its own code comments — plus inline time-sensitive dates.

Suggestions

Move the two full scripts into actual scripts/ bundle files (matching the paths already named in the code comments) and reference them by path, keeping only usage notes, decision logic, and key excerpts inline.

Move the large mapping tables (Step 1 replace-list, Step 2 catalog mapping, Step 4 webhook event map) into references/ files linked one level deep from their steps, shortening SKILL.md to an overview.

Quarantine time-sensitive details — the March 31, 2027 deadline and the November 2026 API-reference snapshot note — in a clearly labeled section so staleness is easy to detect and update.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious domain knowledge (field mappings, event mappings, API quirks) and re-teaches nothing Claude already knows; nearly every table and code block earns its place. Not 5: time-sensitive specifics — "Lemon Squeezy stops processing transactions... on March 31, 2027" and "as of November 2026" — sit inline rather than in a quarantined section, and a few long explanatory passages (e.g. the discounts paragraph) could be tightened. Not 3: there is no padded or generic explanation anywhere.

4 / 5

Actionability

Fully executable throughout: a complete grep command with a key-redacting sed filter, two complete TypeScript scripts (lemon-squeezy-inventory.ts, lemon-squeezy-subscriber-file.ts), SQL DDL for the schema and license tables, an SDK discount-create snippet, the env var block, and the exact run command "node --env-file=.env.local --import tsx scripts/<name>.ts". Copy-paste ready and covering the common cases.

5 / 5

Workflow Clarity

Six explicitly ordered steps, a "Decide with the user first" gate, a cutover sequence with "don't skip ahead", and a "Verify the integration" checklist. Validation feedback loops are present for this batch operation: "open the saved file and compare one subscription... against the field names", "Only clean rows reach the file... then fix the inputs and rerun" via needs-fixing.txt, and post-import reconciliation. Not 4: checkpoints are explicit and recurring, with error-recovery loops at each fragile stage.

5 / 5

Progressive Disclosure

Everything lives in a single ~590-line SKILL.md with no bundle files: the two large scripts are inlined even though the skill itself labels them "// scripts/lemon-squeezy-inventory.ts" and "// scripts/lemon-squeezy-subscriber-file.ts", and the big mapping tables (Step 1 replace-list, Step 2 catalog map, Step 4 webhook map) would fit naturally in references/. Not 2: section structure is strong with clear, well-named headers throughout. Not 4: no references exist at all and the file is far beyond the under-50-line simple-skill exception.

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.

The description is highly specific and distinctive, listing six concrete migration actions in third-person voice with strong natural keywords. Its single gap is the absence of an explicit 'Use when...' trigger clause, leaving the activation condition implied rather than stated.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user wants to move an app selling through Lemon Squeezy to Paddle Billing, or mentions the Lemon Squeezy shutdown or a Paddle migration."

Consider adding one or two natural variations users might say, such as "switch from Lemon Squeezy" or "leave Lemon Squeezy", to strengthen trigger coverage.

DimensionReasoningScore

Specificity

"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" lists six concrete actions in third person, covering every phase of the migration. Not 4: coverage is comprehensive, with only minor gaps — no missing steps relative to the skill's actual scope.

5 / 5

Completeness

The "what" is explicit and detailed, but there is no "Use when..." clause or equivalent explicit trigger guidance; the "when" is only weakly implied by the opening "Move a Lemon Squeezy integration to Paddle Billing". Per the judging guideline, a missing 'Use when' clause caps completeness at 3. Not 4: the when cannot be considered explicit — it requires inference from the action list.

3 / 5

Trigger Term Quality

"Lemon Squeezy", "Paddle Billing", "license keys", "webhooks", "subscriber", and "migration" (via "Move") are exactly the natural terms a user would say when needing this skill, with the two platform names serving as the dominant, unambiguous triggers. Not 4: both product names plus the domain nouns cover the natural vocabulary comprehensively.

5 / 5

Distinctiveness Conflict Risk

"Move a Lemon Squeezy integration to Paddle Billing" carves out a clear niche with distinct triggers; "Lemon Squeezy" is a highly distinctive term unlikely to appear when another billing skill is needed. Not 4: the migration framing plus both platform names leave virtually no overlap risk with generic Paddle-setup skills.

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

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.