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.
74
78%
Does it follow best practices?
Impact
100%
1.14x2 of 3 eval scenarios. Add 1 more for a full score.
Medium
Suggest reviewing before use
Fix and improve this skill with Tessl
tessl review fix ./skills/subscription-update/SKILL.mdW009: 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 a Next.js Server Action that initiates subscription plan changes and charges via the Paddle SDK (`paddle.subscriptions.update()`). This constitutes a direct financial operation (subscription modification and settlement/charges). Access control is independently enforced via Supabase session authentication (`supabase.auth.getUser()`) and admin database ownership verification (`admin.from("subscriptions").select(...)`) prior to calling the SDK.
- Repository
PaddleHQ/paddle-agent-skills
- Revision
70cb70d
- 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.