paddle-subscription-update
Change a Paddle subscription's plan from a Next.js Server Action — auth, ownership check, `prorationBillingMode`, items-array replace semantics, preview-before-commit, and `on_payment_failure` handling.
86
80%
Does it follow best practices?
Impact
96%
1.35xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/subscription-update/SKILL.mdSecurity
1 medium severity finding. This skill can be installed but you should review these findings before use.
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
Direct money access detected (high risk: 1.00). The skill is explicitly built around Paddle's subscription APIs (paddle.subscriptions.update and previewUpdate) and describes invoking those endpoints from a server action to change plans, trigger prorated or full charges, and control on_payment_failure behavior. It requires a server-side PADDLE_API_KEY and details how immediate proration charges are created/handled (transaction.created, transaction.completed, payment failure handling including apply_change). This is a specific payment-gateway integration intended to initiate and control real billing transactions — i.e., it directly moves/charges money.
- Repository
- PaddleHQ/paddle-agent-skills
- Commit
62438cd
- 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.