paddle-customer-portal

Mint a Paddle customer portal session URL from a Next.js Server Action — the portal-vs-custom-billing-screen trade-off, auth, ownership, URL structure (overview vs deep links), and the security model.

Quality

72%

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/customer-portal/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 highly specific and well-targeted skill description that clearly identifies the technology stack (Paddle, Next.js Server Actions) and the concrete concerns it addresses (auth, ownership, URL structure, security model). Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The specificity of the domain makes it naturally distinctive despite this gap.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to integrate Paddle's customer portal, generate billing session URLs, or implement subscription management in a Next.js app.'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions and concepts: minting a Paddle customer portal session URL, using Next.js Server Actions, auth, ownership checks, URL structure with overview vs deep links, and the security model. Also mentions the portal-vs-custom-billing-screen trade-off.	3 / 3
Completeness	Clearly answers 'what does this do' (mint a Paddle customer portal session URL from a Next.js Server Action with specific concerns covered), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric.	2 / 3
Trigger Term Quality	Includes highly specific natural keywords a user would say: 'Paddle', 'customer portal', 'session URL', 'Next.js', 'Server Action', 'billing', 'deep links', 'auth', 'ownership'. These are terms a developer working with Paddle billing integration would naturally use.	3 / 3
Distinctiveness Conflict Risk	Extremely specific niche combining Paddle + customer portal + Next.js Server Actions. This is unlikely to conflict with any other skill given the very targeted technology stack and use case.	3 / 3
	Total	11 / 12 Passed

Implementation

62%

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

The skill excels at actionability with complete, executable code and a clear multi-step workflow with validation checkpoints. However, it is significantly over-verbose — the portal-vs-custom trade-off discussion, the detailed comparison table, and the extensive pitfalls section add substantial token cost for information Claude can largely infer. The content would benefit from aggressive trimming to roughly half its current length while preserving the excellent code examples and security guidance.

Suggestions

Cut the 'Should you use the portal at all?' section to 2-3 sentences max — Claude doesn't need a product strategy lesson to mint a URL.

Condense the 'Common pitfalls' section to a compact bullet list of don'ts (e.g., '- Never accept customerId from client input') without the explanatory paragraphs.

Trim the 'How portal sessions work' prose — the code example and a single sentence about one-time-use URLs is sufficient; the current explanation restates what the code already shows.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~200+ lines. It explains trade-offs Claude already understands (portal vs custom UI), includes a lengthy comparison table, over-explains concepts like 'one-time use URLs,' and has extensive prose in the security model and pitfalls sections that could be condensed to bullet points. The 'Should you use the portal at all?' section alone is unnecessary context padding.	1 / 3
Actionability	The skill provides fully executable, copy-paste-ready code for both the Server Action and the client component. The SDK call signature is concrete, environment variables are specified, and the code includes detailed inline comments explaining each step. The verification steps are specific and testable.	3 / 3
Workflow Clarity	The Server Action code itself is a clearly numbered 5-step workflow with explicit validation at each stage (auth check → customer lookup → subscription lookup → mint session → return URL). The 'Verify the integration' section provides 6 concrete validation checkpoints covering auth, uniqueness, error cases, and security. Error recovery is addressed (no-customer case, no-auth case).	3 / 3
Progressive Disclosure	The skill references related skills (subscription-cancel, subscription-update, subscription-sync) and external docs, which is good. However, the content is monolithic — the lengthy trade-off discussion, security model, and common pitfalls sections could be trimmed or separated. With no bundle files, the inline content is heavier than it needs to be for a single-purpose skill.	2 / 3
	Total	9 / 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: 62438cd

Reviewed: about 19 hours 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.