Tessl • The management layer for AI agent skills

An excellent single-file skill: fully executable code with hard-won Paddle-specific gotchas, a clear prerequisites-to-verification flow, an explicit verification checklist, and error-recovery pitfalls. The only notable costs are the general-MCP digression and the absence of any reference-file split for the events table.

Dimension	Reasoning	Score
Conciseness	The body is dense with Paddle-specific, non-obvious gotchas ('frameTarget is a CSS class name (no leading dot)', 'a relative URL passed to initializePaddle is dropped') and assumes Next.js/React competence, but the MCP conventions blockquote (camelCase/snake_case, pagination, caps) is general MCP usage rather than checkout-specific and could be trimmed. Anchor 4 fits: efficient overall with minor over-explanation; not 5 because of the MCP digression, not 3 because the bulk is lean and every section adds non-inferable detail.	4 / 5
Actionability	Two complete, copy-paste-ready TSX components with install commands, env vars, exact dashboard navigation paths, and a concrete sandbox test card. Fully executable guidance covering the common cases (overlay minimum, inline with events, pre-fill, dynamic items).	5 / 5
Workflow Clarity	Clear sequence from prerequisites through the minimum overlay path to the full inline pattern, an explicit 'Verify the integration' checklist with expected outcomes at each step, and a 'Common pitfalls' section that serves as error-recovery guidance. This is a non-destructive client-side skill, so no destructive-operation cap applies.	5 / 5
Progressive Disclosure	No bundle files exist; all content is inline in a single well-sectioned ~320-line file that is easy to navigate and defers full event/API detail to external doc links. Minor gaps: the events reference table and the MCP conventions blockquote could live in separate reference files, which keeps this below anchor 5's 'appropriately split' structure.	4 / 5
	Total	18 / 20 Passed

Description

66%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, mostly well-scoped description that names the domain, the framework, and several concrete capabilities in third person. Its main weakness is the absence of an explicit 'Use when...' trigger clause and of common payment/billing synonyms, which limits discoverability and completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when adding Paddle checkout, payment, or subscription flows to a Next.js app.'

Include natural synonyms such as 'payment', 'billing', 'subscription', and 'Paddle.js' so users' phrasing matches the trigger terms.

Optionally mention the post-checkout success redirect in the capability list to round out coverage of what the skill does.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('overlay or inline, with event handling, customer pre-fill, and dynamic line item updates') with concrete style options, but minor gaps in coverage (no mention of the post-checkout success redirect, checkout variants, or verification).	4 / 5
Completeness	The 'what' is clear (add a Paddle checkout to a Next.js app with the listed capabilities), but there is no 'Use when...' clause or equivalent explicit trigger guidance; the 'when' is only weakly implied. Per the rubric guideline, a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	'Paddle Checkout' and 'Next.js' are natural phrases a user would say, giving good keyword coverage, but common synonyms like 'payment', 'billing', 'subscription', or 'Paddle.js' are missing.	4 / 5
Distinctiveness Conflict Risk	'Paddle Checkout' plus 'Next.js web app' carves a clear niche distinct from generic checkout work, but sibling Paddle skills (webhooks, catalog-setup, subscription-sync) create minor overlap risk on the bare 'Paddle' term.	4 / 5
	Total	15 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: PaddleHQ/paddle-agent-skills
Path: providers/cursor/plugin/skills/checkout-web/SKILL.md
Revision: 70cb70d

Reviewed: 4 days ago

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.

paddle-checkout-web

Table of Contents

Is this your skill?