CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/pricing-pages/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

A highly actionable, well-structured skill body with complete executable code, a verification checklist, and strong gotcha coverage. Minor conciseness trims and an explicit error-recovery loop would push it higher.

DimensionReasoningScore

Conciseness

Mostly lean, dense, specific content (exact code, gotchas, pitfalls) with minor over-explanation that could be trimmed, notably the "Why use PricePreview at all?" rationale section and the trailing MDN Intl note.

4 / 5

Actionability

Fully executable, copy-paste-ready TypeScript/TSX for the hook, pricing component, country detection, parse-money utils, and subscribe handler, covering the common cases with real API field names.

5 / 5

Workflow Clarity

Clear sequence (prerequisites → tiers → hook → component → detection → formatting → checkout → pitfalls) with an explicit 6-step "Verify the integration" checklist; minor gap is the lack of an explicit validate→fix→retry feedback loop.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and one-level-deep external doc links under "Related docs"; no bundle files exist to split into, and content is cohesive inline, with only minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

70%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, well-scoped description with concrete actions and natural trigger terms, but it omits an explicit "Use when..." clause, which caps completeness. Distinctiveness is strong.

Suggestions

Add an explicit trigger clause, e.g. "Use when building a Next.js pricing page that must show prices in the user's local currency."

Consider mentioning tax/checkout-sync behavior briefly so the "what" matches the body's full scope.

Add a common synonym like "regional pricing" or "local currency" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names the domain (Next.js pricing page, Paddle.js PricePreview) plus several concrete actions — "country detection, billing frequency toggle, and currency formatting" — with only minor gaps (tax behavior and checkout-sync are covered in the body, not the description).

4 / 5

Completeness

The description gives a clear "what" (render localized prices via PricePreview with detection/toggle/formatting) but has no explicit "Use when..." trigger clause, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Natural phrases users would say are present ("pricing page", "country-localized prices", "currency formatting") alongside the technical "Paddle.js PricePreview"; a few common synonyms like "regional pricing" or "local currency" are missing.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — displaying country-localized prices on a Next.js pricing page via PricePreview — distinct from the related checkout skill, with minimal conflict risk.

5 / 5

Total

16

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
PaddleHQ/paddle-agent-skills
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.