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.

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/pricing-pages/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 complete, executable code examples covering the full pricing page workflow. Its main weakness is verbosity — several sections (MCP server details, 'Why use PricePreview', some pitfall explanations) add tokens without proportional value for Claude. The workflow is well-sequenced with good validation steps, though the content length suggests some material could be offloaded to supporting files.

Suggestions

Remove or drastically shorten the 'Why use PricePreview at all?' section — Claude doesn't need to be convinced of the API's value, just told when and how to use it.

Move the MCP server paragraph to a separate reference file or reduce to a single line cross-reference — it's tangential to the main client-side pricing skill.

Consider extracting the currency parsing utility (`parse-money.ts`) and country selector component into bundle files, referencing them from the main skill to reduce inline length.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with good code examples, but includes some unnecessary explanation (e.g., 'Why use PricePreview at all?' section explaining why hardcoding is bad, the lengthy MCP server paragraph, and some verbose pitfall descriptions). The content could be tightened by ~20-30% without losing actionable value.	2 / 3
Actionability	Excellent actionability — provides fully executable TypeScript/TSX code for the hook, pricing component, country selector, currency parsing utility, and checkout integration. Code is copy-paste ready with proper imports, types, and real API patterns.	3 / 3
Workflow Clarity	The skill follows a clear logical sequence: define tiers → create hook → build component → detect country → handle currency formatting → integrate checkout. The 'Verify the integration' section provides explicit validation checkpoints covering edge cases (zero-decimal currencies, VAT, sandbox vs production).	3 / 3
Progressive Disclosure	The skill references related skills (`checkout-web`, `catalog-setup`) and external docs appropriately, but the content itself is quite long (~300+ lines) with sections like the MCP server paragraph and detailed currency formatting utilities that could be split into separate reference files. The inline country selector component and money parsing utility could live in referenced files.	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 strong, specific description that clearly identifies the technology stack (Next.js, Paddle.js PricePreview) and lists concrete capabilities (country detection, billing frequency toggle, currency formatting). 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 building or modifying a pricing page with Paddle, implementing localized pricing, or adding billing frequency toggles in a Next.js app.'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'country-localized prices', 'country detection', 'billing frequency toggle', and 'currency formatting' — all concrete, actionable capabilities.	3 / 3
Completeness	Clearly answers 'what does this do' with specific capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'pricing page', 'Next.js', 'Paddle', 'PricePreview', 'country detection', 'billing frequency toggle', 'currency formatting', 'localized prices'. These cover the domain well.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — the combination of Next.js, Paddle.js PricePreview, country-localized pricing, and billing frequency toggle creates a very specific niche that is unlikely to conflict with other 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.