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.
69
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 application.'
| 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 conflicts with other skills highly unlikely. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%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, well-structured skill that provides highly actionable guidance for integrating Paddle checkout in Next.js. The code examples are complete and production-ready, the workflow is clearly sequenced with verification steps, and progressive disclosure is handled well with appropriate cross-references. The main weakness is moderate verbosity — some explanatory text and tables could be trimmed without losing clarity, and the MCP server paragraph feels tangential to the core checkout skill.
Suggestions
Trim or move the MCP server paragraph to a separate reference — it's a large block of tangential information that interrupts the checkout flow.
Remove the 'Choose your checkout variant' table or fold it into a single line within the settings explanation, since it just describes one config option (variant: 'one-page' vs 'multi-page').
| 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 checkout variant table that adds little actionable value). Some sections like 'Post-checkout: redirect vs webhook' explain concepts Claude likely already understands. | 2 / 3 |
Actionability | Excellent 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 working throttle patterns. The code examples are complete and production-realistic. | 3 / 3 |
Workflow Clarity | The skill clearly sequences the workflow: prerequisites → choose style → implement (with two clear paths) → customer pre-fill → dynamic items → event handling → post-checkout → verification. The verification section provides an explicit 5-step checklist with validation checkpoints including confirming events fired and dashboard state. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections progressing from simple (overlay) to complex (inline with full event handling). References to related skills (webhooks, subscription-sync, sandbox-testing, catalog-setup) and external docs are clearly signaled and one level deep. The skill appropriately keeps checkout-specific content inline while pointing elsewhere for server-side concerns. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%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
62438cd
- 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.