paddle-checkout-web

Add a Paddle Checkout to a Next.js web app — overlay or inline, with event handling, customer pre-fill, and dynamic line item updates.

Quality

80%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/checkout-web/SKILL.md

Quality

Discovery

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong, specific description that clearly identifies the technology stack (Paddle + Next.js) and lists concrete capabilities. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The specificity and distinctiveness are excellent.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user wants to integrate Paddle payments, add a checkout flow, or set up billing in a Next.js app.'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'overlay or inline' checkout modes, 'event handling', 'customer pre-fill', and 'dynamic line item updates'. These are concrete, actionable capabilities.	3 / 3
Completeness	Clearly answers 'what does this do' (add Paddle Checkout with specific features), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric.	2 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'Paddle', 'Checkout', 'Next.js', 'overlay', 'inline', 'line item', 'customer pre-fill'. These are terms a developer would naturally use when seeking payment integration help.	3 / 3
Distinctiveness Conflict Risk	Very distinct niche: specifically Paddle (not Stripe, not generic payments) combined with Next.js. The combination of a specific payment provider and framework makes it highly unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Implementation

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, highly actionable skill with complete, executable code examples for both overlay and inline Paddle checkout patterns in Next.js. The workflow is well-sequenced with a clear verification checklist. The main weakness is verbosity — several sections (MCP paragraph, variant table, some pitfall explanations) could be trimmed or extracted to keep the main skill leaner.

Suggestions

Extract the Paddle MCP server usage note into a separate referenced file or collapse it into a 2-line summary with a pointer, as it's tangential to the core checkout skill.

Consider moving the 'Common pitfalls' section to a separate PITFALLS.md or TROUBLESHOOTING.md file and linking to it, keeping only the top 2-3 most critical pitfalls inline.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with good code examples and tables, but includes some unnecessary explanation (e.g., the lengthy Paddle MCP server paragraph, explaining what overlay vs inline looks like, the checkout variant table that adds little actionable value, and some verbose pitfall descriptions). The 'When to use this skill' section restates what the title already conveys.	2 / 3
Actionability	Provides fully executable, copy-paste-ready TSX code for both overlay and inline checkout patterns, concrete environment variable names, specific npm install commands, real type imports, and specific test card numbers. The code examples are complete and production-realistic with proper TypeScript typing.	3 / 3
Workflow Clarity	The skill follows a clear progression: prerequisites → choose style → minimal overlay implementation → full inline implementation → customization options → verification. The verification section provides an explicit 5-step checklist with specific validation criteria (price matches, event fires, transaction appears in dashboard). Error recovery is addressed in the pitfalls section.	3 / 3
Progressive Disclosure	The skill references related skills (webhooks, subscription-sync, sandbox-testing, catalog-setup) and external docs, which is good. However, the content is quite long (~250 lines) and could benefit from splitting the inline checkout example, event reference table, and pitfalls into separate files. The MCP server usage note is a large inline block that could be a separate reference.	2 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: PaddleHQ/paddle-agent-skills
Commit: 86596b3

Reviewed: 16 days ago

Table of Contents

Discovery Implementation Validation

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.