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.
61
77%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Medium
Suggest reviewing before use
Fix and improve this skill with Tessl
tessl review fix ./providers/cursor/plugin/skills/customer-portal/SKILL.mdThe canonical home for this skill is paddle-customer-portal in PaddleHQ/paddle-agent-skills
W009: Direct money access capability detected (payment gateways, crypto, banking).
What this means
The skill is specifically designed for direct financial operations, giving the agent the ability to move money or execute financial transactions — such as payment processing, cryptocurrency operations, banking integrations, or market order execution.
Why it was flagged
The skill documents minting Paddle customer portal session URLs using the Paddle SDK (`paddle.customerPortalSessions.create`). This creates a hosted management session URL for viewing invoices, updating payment methods, and managing subscriptions, which constitutes a financial billing/subscription management workflow. However, it does not perform direct financial transfers, charges, refunds, or purchases itself; it provides indirect redirection/session generation for customer self-service. Therefore, it falls under indirect financial operations.
- Audited
- Security analysis
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.