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

Fix and improve this skill with Tessl

tessl review fix ./skills/checkout-web/SKILL.md

Quality

Content

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 excellent executable code examples covering both overlay and inline Paddle checkout patterns in Next.js. The workflow is well-sequenced with clear verification steps and a comprehensive pitfalls section. The main weakness is length — at ~250 lines with no bundle files for progressive disclosure, it's a dense monolithic document that could benefit from splitting advanced topics (inline checkout, MCP usage, event handling) into separate referenced files, and trimming some explanatory content Claude doesn't need.

Suggestions

Trim the MCP server paragraph — it's a large block of operational detail that could be a separate reference file or condensed to 2-3 lines with a pointer.

Consider splitting the inline checkout example and event handling into a separate INLINE.md file, keeping SKILL.md focused on the overlay quick-start and linking out for the advanced pattern.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with good code examples and tables, but includes some unnecessary explanation (e.g., the lengthy MCP server paragraph, explaining what overlay vs inline looks like, the 'Choose your checkout variant' section that adds little actionable value). The prerequisites section is thorough but could be tighter. Some sections like 'Post-checkout: redirect vs webhook' explain concepts Claude likely understands.	2 / 3
Actionability	Excellent actionable content throughout — fully executable TypeScript/TSX code examples for both overlay and inline checkout, specific npm install commands, concrete environment variable names, real API method signatures, and copy-paste ready patterns including the throttled updateItems pattern. The code examples are complete and production-ready.	3 / 3
Workflow Clarity	The skill provides clear sequential workflows: prerequisites → choose style → implement → verify. The verification section has explicit numbered steps with specific test card numbers and expected outcomes. The common pitfalls section serves as an effective troubleshooting checklist. The inline example shows proper initialization guards (paddle?.Initialized) as validation checkpoints.	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 monolithic — the MCP server usage note, the full inline checkout example, and the common pitfalls could potentially be split into referenced files. Without bundle files, all content is inline, making it a dense single document.	2 / 3
	Total	10 / 12 Passed

Description

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 well-crafted description with strong specificity and excellent trigger terms that clearly identify the technology stack (Paddle + Next.js) and 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 over others.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user wants to integrate Paddle payments, add a checkout flow, or handle 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	Highly distinctive — the combination of 'Paddle' (specific payment provider) + 'Checkout' + 'Next.js' creates a very clear niche that is unlikely to conflict with other skills like generic payment or generic Next.js skills.	3 / 3
	Total	11 / 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: 72e6fdf

Reviewed: 20 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.