CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

paddle-pricing-pages

Render country-localized prices on a Next.js pricing page using Paddle.js PricePreview — country detection, billing frequency toggle, and currency formatting.

68

Quality

85%

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

The canonical home for this skill is paddle-pricing-pages in PaddleHQ/paddle-agent-skills

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 excellent, highly actionable skill: complete executable code for every component, a real verification checklist with error-recovery guidance, and dense coverage of non-obvious Paddle gotchas. Only minor conciseness trims and potential content-splitting of the general MCP reference keep it from full marks.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious gotchas (zero-decimal currencies, the OTHERS sentinel, reusing formattedTotals, sandbox/production IDs) and avoids explaining known concepts, but the long general Paddle-MCP blockquote and some "Why use PricePreview" prose are minor over-explanations that could be trimmed — anchor 4, not 5.

4 / 5

Actionability

Every layer ships complete, copy-paste-ready TypeScript: tier constants, the usePaddlePrices hook, the pricing component, server-side country detection, the country selector, money-parsing utils, and the checkout handler, plus concrete verification steps — fully matching anchor 5.

5 / 5

Workflow Clarity

A logical build sequence (prerequisites → tiers → hook → component → detection → formatting → checkout → pitfalls) is capped by an explicit 6-step "Verify the integration" checklist with expected outcomes and a feedback loop (step 5 tells the reader to prefill the country if the currency mismatches), matching anchor 5.

5 / 5

Progressive Disclosure

The single-file body is well-organized with clear section headers and clearly signaled one-level-deep external doc links (no bundle files exist), but content like the general Paddle-MCP reference blockquote and the currency-decimals helper could be split into separate reference files — good structure with minor organization gaps, anchor 4.

4 / 5

Total

18

/

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, distinctive description with strong concrete capability phrasing, undermined by the absence of any explicit "Use when..." trigger clause. Adding a trigger sentence would raise completeness from 3 to 5.

Suggestions

Append an explicit trigger clause, e.g. "Use when building a pricing or upgrade page that must show prices in the visitor's local currency, or when the user mentions Paddle, localized/regional pricing, or currency formatting."

Include a few natural synonyms users would say — "local currency", "regional pricing", "localized pricing" — to broaden trigger-term coverage from good to comprehensive.

Optionally mention the monthly/yearly toggle in user language ("show monthly vs yearly prices") since that is a common way the request is phrased.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Render country-localized prices", "country detection, billing frequency toggle, and currency formatting" — giving comprehensive coverage of the skill's scope, matching the anchor-5 pattern of several specific gerund-phrase capabilities.

5 / 5

Completeness

The "what" is clear (render country-localized prices via Paddle.js PricePreview with three named sub-capabilities), but there is no "Use when..." clause or equivalent explicit trigger guidance — "on a Next.js pricing page" only weakly implies when — which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural terms like "pricing page", "Paddle", "Next.js", "currency", and "billing frequency" are present, but a few natural user phrasings (e.g. "local currency", "regional pricing") are missing, matching anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche is highly distinct — "Paddle.js PricePreview" on a "Next.js pricing page" — with minimal conflict risk against non-Paddle skills, and naming PricePreview specifically avoids overlap with sibling Paddle skills like checkout.

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

providers/claude/plugin/skills/pricing-pages/SKILL.md

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.