CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 integration guide with strong verification and error-recovery guidance. Its weaknesses are token efficiency and file structure: tooling digressions and dense prerequisites are inlined in a monolithic SKILL.md instead of being offloaded to reference files.

Suggestions

Move the Paddle MCP and Paddle CLI blockquote paragraphs into a reference file (e.g. references/paddle-tooling.md), keeping only a one-line pointer in the body.

Extract the domain-approval and default-payment-link details from Prerequisites into a reference file, retaining the short checklist inline.

Consolidate the version requirements (paddle-js 1.6.4+/1.6.5+/1.6.1, CLI v0.2.0) into a single compatibility note rather than scattering them across sections.

DimensionReasoningScore

Conciseness

The body is mostly dense, non-obvious operational knowledge (domain approval, successUrl gotchas, event shapes) with no basic-concept padding, but the two long MCP/CLI blockquote paragraphs, the very long prerequisites bullets, and inline version pins (1.6.4+, 1.6.5+, v0.2.0) could be tightened or split out.

3 / 5

Actionability

Two complete copy-paste-ready React components, exact install commands, env var setup with dashboard locations, a sandbox test card number, and pitfalls each paired with a concrete fix fully cover the common cases.

5 / 5

Workflow Clarity

The skill sequences prerequisites → style choice → integration → events → post-checkout, with an explicit "Verify the integration" checklist and error-recovery loops (e.g. checkout_url_domain_not_approved → add domain → retry; frameTarget mismatch fix).

5 / 5

Progressive Disclosure

Section structure and external doc links are good, but this is a single ~320-line file with no reference bundle; the MCP/CLI tooling paragraphs and domain-approval details are inline content that clearly belongs in separate reference files.

3 / 5

Total

16

/

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 specific, well-scoped description with concrete capabilities and clear niche boundaries. Its main weakness is the absence of an explicit 'when to use' trigger clause, which both caps completeness and thins natural trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when adding Paddle payments or a buy/checkout flow to a Next.js app."

Include one or two natural user phrasings (payment, billing, buy button) to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"Add a Paddle Checkout... overlay or inline", "event handling", "customer pre-fill", "dynamic line item updates" are multiple concrete actions comprehensively covering this integration's surface, matching the top anchor's breadth rather than the 'minor gaps' of anchor 4.

5 / 5

Completeness

The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural terms like "Paddle Checkout", "Next.js", "overlay", "inline", "customer pre-fill", and "line item updates" are present, but common user phrasings such as "payment", "billing", or "buy button" are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

"Paddle Checkout" plus "Next.js" carves a clear niche with distinct triggers and minimal conflict risk; it would not fire for sibling skills like webhooks or subscription-sync.

5 / 5

Total

17

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

PaddleHQ/paddle-agent-skills

Path

skills/checkout-web/SKILL.md

Revision

f2e0af8

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill