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?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/pricing-pages/SKILL.md

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable code and a strong verification checklist, but it leans slightly verbose in its motivational sections and keeps everything inline rather than splitting reference material into bundle files. Tightening rationale prose and externalizing the MCP reference would lift the weaker dimensions.

Suggestions

Trim the 'Why use PricePreview at all?' rationale to one or two sentences or move it to a reference file to improve conciseness.

Move the Paddle MCP usage blockquote into a references/ file (e.g. references/paddle-mcp.md) and link to it, improving progressive disclosure.

Consider extracting the full pricing-page component and country-selector code into a bundled example file, keeping SKILL.md as an overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with dense, actionable code and gotchas, but sections like 'Why use PricePreview at all?' and the large MCP blockquote add motivational/contextual padding that could be tightened; not a 3 because not every token earns its place.	2 / 3
Actionability	Provides fully executable, copy-paste-ready code for the hook, page component, country detection, currency parsing, and checkout handoff, with specific API field references.	3 / 3
Workflow Clarity	Clear build sequence (tiers → hook → component → country detection → formatting → checkout) plus an explicit numbered 'Verify the integration' checklist with concrete validation steps and error signals.	3 / 3
Progressive Disclosure	Single-file skill with no bundle files; content is well-sectioned with one-level-deep external doc links, but substantial inline material (e.g. the MCP blockquote, full component code) that could be split out keeps it at 2 rather than 3.	2 / 3
	Total	10 / 12 Passed

Description

82%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, distinctive, and uses natural trigger terms, but it omits an explicit 'Use when...' clause so it does not fully answer when Claude should invoke the skill. Voice is correctly third person. Adding a brief trigger clause would raise completeness.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when building a Next.js pricing page that must show country-localized prices, handle a monthly/yearly toggle, or format zero-decimal currencies.'

Add common user phrasings like 'local currency', 'localized pricing', or 'tax-inclusive pricing' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'country detection, billing frequency toggle, and currency formatting' anchored on 'Render country-localized prices on a Next.js pricing page using Paddle.js PricePreview' — matching the multi-action anchor.	3 / 3
Completeness	Clearly states what the skill does, but lacks an explicit 'Use when...' trigger clause; per the guidelines a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	Uses natural terms a user would say — 'pricing page', 'prices', 'country-localized', 'currency formatting', 'Next.js' — giving good coverage of common phrasings.	3 / 3
Distinctiveness Conflict Risk	The Paddle.js PricePreview + Next.js pricing-page niche is highly specific with distinct triggers, making conflict with other skills unlikely.	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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: PaddleHQ/paddle-agent-skills
Path: skills/pricing-pages/SKILL.md
Commit: cbd404f

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