CtrlK
BlogDocsLog inGet started
Tessl Logo

paddle-billing-history

Render the authenticated user's billing history in Next.js — listing transactions via the Paddle Node SDK, the mandatory customer-id filter, pagination via `.next()`/`.hasMore`, status filtering, and formatting raw transaction totals (lowest-unit conversion + Intl.NumberFormat, with the zero-decimal currency special case for JPY/KRW/CLP).

69

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, well-sequenced skill body with executable code and strong verification steps. The only weakness is moderate redundancy around the zero-decimal currency trap, which slightly hurts token efficiency.

Suggestions

Consolidate the zero-decimal currency (JPY/KRW/CLP) guidance into one canonical location and reference it from the pitfalls section rather than restating the full explanation three times.

The 'Common pitfalls' list largely reiterates traps already covered in 'Common formatting traps' and the inline code comments — consider trimming duplicates to keep the pitfalls section a terse checklist.

DimensionReasoningScore

Conciseness

The body is mostly efficient and focused on non-obvious Paddle SDK specifics Claude would not reliably know, but the zero-decimal currency trap is restated three times (inline comment, formatting traps, common pitfalls) and could be tightened.

2 / 3

Actionability

Provides a fully executable Server Action, a parseMoney/convertAmountFromLowestUnit helper, and a client pagination component — all copy-paste ready with specific details.

3 / 3

Workflow Clarity

The action is numbered 1–5 with inline rationale, and the 'Verify the integration' section supplies explicit checkpoints including a critical cross-customer security verification step.

3 / 3

Progressive Disclosure

No bundle files exist; the single SKILL.md is organized into clearly headed sections (prerequisites, action, status filter, formatting, pagination, pitfalls, verify) with one-level external links, satisfying the simple-skill allowance for well-organized single-file skills.

3 / 3

Total

11

/

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.

A specific, third-person description with concrete capabilities and good trigger terms for a well-defined niche. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which leaves the when implicit.

Suggestions

Add an explicit trigger clause such as 'Use when adding a Billing history or Invoices section to an authenticated Next.js account page' to clearly state when Claude should invoke the skill.

Consider including common phrasings a user might say ('billing history', 'invoices', 'transaction history', 'payment history') earlier in the description to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'listing transactions via the Paddle Node SDK, the mandatory customer-id filter, pagination via .next()/.hasMore, status filtering, and formatting raw transaction totals', matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

The what is thoroughly described, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

Natural developer-facing terms like 'billing history', 'transactions', 'Next.js', and 'Paddle Node SDK' align with what a user would say, satisfying good coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

The Paddle + Next.js + billing-history niche is highly specific and written in third person ('Render'), making it unlikely to trigger for the wrong skill.

3 / 3

Total

11

/

12

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.