Guide for upgrading Stripe API versions and SDKs
72
58%
Does it follow best practices?
Impact
100%
1.51xAverage score across 3 eval scenarios
High
Do not use without reviewing
Fix and improve this skill with Tessl
tessl review fix ./providers/claude/plugin/skills/upgrade-stripe/SKILL.mdThe canonical home for this skill is upgrade-stripe in stripe/ai
Security
2 findings: 1 high severity, 1 medium severity. You should review these findings carefully before considering using this skill.
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
The prompt contains examples that embed API secret-like strings (e.g., "sk_test_xxx") directly in code and curl commands, which instructs the LLM to output credential values verbatim and therefore creates an exfiltration risk.
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.
The document is an upgrade guide for the Stripe payment gateway and includes explicit Stripe API usage: SDK initializations with secret keys, a curl request to the Stripe /v1/customers endpoint, and example API calls (e.g., stripe.Customer.create). These are specific payment-gateway API interactions that enable direct financial operations via Stripe, so this skill grants Direct Financial Execution capability.
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.