upgrade-stripe
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.mdSecurity
2 findings — 1 high severity, 1 medium severity. You should review these findings carefully before considering using this skill.
W007: Insecure credential handling detected in skill instructions
What this means
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.
Why it was flagged
Insecure credential handling detected (high risk: 0.90). The prompt includes examples that embed API keys directly (e.g., 'sk_test_xxx' in code and curl -u), and it instructs using literal credentials in commands/configuration which would require an LLM to copy or insert secrets verbatim—an unsafe pattern prone to exfiltration.
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 about Stripe (a payment gateway) and includes concrete Stripe API usage: initializing clients with secret keys, per-request version overrides, example curl and SDK calls (e.g., creating a customer via https://api.stripe.com/v1/customers), and references to Payments/Billing/Connect. This is a specific, payment-gateway integration guide (not a generic tool), so it grants direct financial execution capability.