Guide for upgrading Stripe API versions and SDKs
62
43%
Does it follow best practices?
Impact
91%
1.16xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./providers/claude/plugin/skills/upgrade-stripe/SKILL.mdNode.js Stripe SDK version upgrade
Correct API version string
100%
100%
Explicit apiVersion in constructor
100%
100%
No default-reliance pattern
100%
100%
SDK package version updated
100%
100%
Stripe-Version header testing documented
100%
100%
Changelog review mentioned
100%
100%
SDK update command referenced
100%
100%
Per-request override explained
100%
100%
Webhook considerations noted
0%
100%
Staged adoption awareness
50%
62%
Go strongly-typed Stripe SDK upgrade
No hardcoded API version string
100%
100%
SDK module version bumped
100%
100%
Correct upgrade rationale documented
53%
100%
Contrast with dynamic languages
58%
100%
Changelog review step included
100%
100%
Breaking change tagging mentioned
0%
0%
Upgrade steps listed
100%
100%
SDK update mechanism correct
100%
100%
Import path updated
100%
100%
Backward-compatible change awareness
50%
33%
Stripe.js, database schema, and webhook upgrade
Stripe.js Dahlia script URL
100%
100%
No API version override in JS
100%
100%
Stripe ID columns widened to 255
100%
100%
Case-sensitive collation applied
0%
100%
Webhook unknown event handling
100%
100%
Stripe.js version pairing documented
20%
100%
ID size rationale documented
100%
100%
Stripe.js npm alternative mentioned
0%
0%
Webhook testing step included
0%
0%
At least 6 bullet points in report
100%
100%
Table of Contents
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.