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

82%

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 genuine feedback loops and validation for its batch and destructive operations. Its weaknesses are length in a single monolithic file — the scripts and mapping tables belong in separate bundle files — and a few passages that could be tightened.

Suggestions

Move the two full TypeScript scripts (lemon-squeezy-inventory.ts, lemon-squeezy-subscriber-file.ts) into a scripts/ bundle directory, keeping only their usage and edge-case notes inline.

Move the large Lemon Squeezy→Paddle mapping tables (Step 1 touchpoints, Step 2 catalog rules, Step 4 webhook events) into a references/ file, summarizing the key rules inline.

Trim explanatory prose inside table cells (e.g. the checkout-parameters and status-mapping rows) to the mapping itself plus a one-line caveat.

DimensionReasoningScore

Conciseness

The body is dense with migration-specific facts Claude cannot know ("Lemon Squeezy retried a webhook only three times", "Sandbox and live are separate: IDs from one don't exist in the other") and never explains known concepts, but at ~590 lines a few table cells and prose passages (e.g. the checkout-parameter row explanations) could be trimmed — efficient with minor instances of over-length rather than the 'every token earns its place' anchor.

4 / 5

Actionability

Fully executable throughout: two complete runnable TypeScript scripts, a copy-paste grep/sed audit command, SQL DDL for the schema changes, an SDK discount snippet, exact env vars, and API key permissions — covering the common cases concretely.

5 / 5

Workflow Clarity

Six clearly ordered steps with explicit validation checkpoints and feedback loops: "anything a script can't place goes in `needs-fixing.txt`", "fix the inputs rather than the output and the import-day rerun stays complete", a dedicated "Verify the integration" section, sandbox-first creation, and a gated cutover order — validation is present for the batch subscriber-file and cancellation operations.

5 / 5

Progressive Disclosure

Section headers and step structure are clear, but no bundle files exist and content that would be better split out — the two full TypeScript scripts (~130 lines) and the large mapping tables — is inlined in a ~590-line single file, fitting the 'content that should be separate is inline' anchor rather than the well-split anchor above it.

3 / 5

Total

17

/

20

Passed

Description

75%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 concretely enumerates the migration's actions. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which both caps completeness and leaves a few natural user phrasings uncovered.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to move, switch, or migrate from Lemon Squeezy to Paddle Billing".

Include a few natural synonyms users might say, such as "switch off Lemon Squeezy" or "move subscriptions to Paddle", to strengthen trigger coverage.

DimensionReasoningScore

Specificity

The description enumerates six 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" — comprehensively covering the skill's steps, matching the top anchor rather than the 'minor gaps' anchor below it.

5 / 5

Completeness

The "what" is explicit and multi-part, but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines; it is above a vague 'what' (anchor 2) because the actions are concrete.

3 / 5

Trigger Term Quality

"Lemon Squeezy", "Paddle Billing", "webhooks", "license keys", and "subscriber file" are the natural terms a user would say, but common variations like "switch" or "move off Lemon Squeezy" aren't covered — good coverage with a few natural terms missing, so not the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

"Move a Lemon Squeezy integration to Paddle Billing" names both the source and target platform, a clear niche with distinct triggers and minimal conflict risk with any other skill.

5 / 5

Total

17

/

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/cursor/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.