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.
82%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Medium
Suggest reviewing before use
The canonical home for this skill is paddle-migrate-lemon-squeezy in PaddleHQ/paddle-agent-skills
The skill is specifically designed for direct financial operations, giving the agent the ability to move money or execute financial transactions — such as payment processing, cryptocurrency operations, banking integrations, or market order execution.
No direct payment operation is established. The skill builds a Paddle catalog, discounts, an ID map, webhook handlers and license-key storage. It never transfers funds, charges, refunds, or cancels. Its Lemon Squeezy calls are read-only `GET`s (line 28), and the payment-details transfer is left to a migration specialist (lines 27, 413). Catalog and discount creation is configuration, and checkout and webhook code are implementation guidance, which is excluded. The indirect route is Step 6. It builds a subscriber file of active, card-paid subscriptions with Paddle price IDs, next billing dates and discounts, which is handed off for Paddle-assisted import (lines 399, 524-535, 550, 564). Those imported subscriptions then generate real recurring charges on Paddle. This is preparation of billing instructions for downstream execution, so it is treated as indirect. Under the recall-first override, that ambiguity is resolved toward the higher tier. Because there is no direct operation, no access-control analysis applies, and the severity is medium rather than high.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The required workflow bulk-pulls the store's customers, subscriptions, orders, and discount data from the Lemon Squeezy API (Step 2) and builds the subscriber file from them, including customer-entered free text such as `user_name` and `user_email`, without the agent selecting a specific item, so an outsider who checks out can place text into records the workflow reads.
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.