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

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/pricing-pages/SKILL.md

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 (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. The description uses proper third-person voice and avoids vague language.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to build or modify a pricing page with Paddle, display localized prices, or implement billing frequency toggles in Next.js.'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'country-localized prices', 'country detection', 'billing frequency toggle', and 'currency formatting' on a 'Next.js pricing page using Paddle.js PricePreview'.	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 dimension at 2 per the rubric.	2 / 3
Trigger Term Quality	Includes strong natural keywords a user would say: 'pricing page', 'Next.js', 'Paddle', 'PricePreview', 'country detection', 'billing frequency toggle', 'currency formatting', 'localized prices'. These cover the likely terms a developer would use.	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 clear niche that is unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Implementation

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 implementation. The workflow is well-sequenced with good validation steps. Main weaknesses are moderate verbosity (the 'Why use PricePreview' rationale section, the lengthy MCP paragraph) and the monolithic structure that could benefit from splitting some content into supporting files.

Suggestions

Trim or remove the 'Why use PricePreview at all?' section — Claude doesn't need persuading on when to use an API; the 'When to use this skill' section already covers this.

Move the MCP server paragraph to a separate reference file or collapse it into a brief one-line note with a cross-reference, as it's tangential to the main client-side pricing flow.

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. The tier constants, hook, and component form a complete implementation.	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 (network inspection, currency switching, checkout confirmation, sandbox vs production). Error recovery is addressed in the pitfalls section.	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 everything inline. The MCP server block and currency formatting utility could be split into referenced files. However, since no bundle files are provided, the inline approach is the only option, and the section headers provide reasonable navigation.	2 / 3
	Total	10 / 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: 86596b3

Reviewed: 16 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.