What does this skill do, and when should you use it?
This skill provides focused guidance for upgrading Stripe API versions and related SDKs. It covers breaking and backward-compatible changes, dynamically typed and strongly typed server-side SDKs, Stripe.js, iOS, Android, and React Native. It recommends targeting API version 2026-06-24.dahlia unless the user specifies another target. The guide also includes an upgrade checklist, testing examples, and webhook compatibility advice.
It distinguishes backward-compatible from breaking Stripe API changes, directs users to the API Changelog and upgrades guide, and explains how to update server-side SDKs, apiVersion settings, Stripe.js, mobile SDKs, and webhook handlers. It provides configuration and testing examples in Python, Ruby, JavaScript, and curl. For strongly typed languages, it explains that the SDK should be upgraded to match the target API version rather than overriding the API version directly.
- A Python, Ruby, PHP, or Node.js developer needs to set an explicit Stripe API version.
- A Java, Go, or .NET team needs to migrate through an SDK release that targets a newer API version.
- A frontend developer maintains a Stripe.js integration and needs to move between Acacia, Basil, Clover, or Dahlia releases.
- An iOS, Android, or React Native team needs guidance for planning a mobile SDK upgrade.
- An engineer wants to test a new API version with the Stripe-Version header before changing the default.
- A Stripe integration maintainer needs to review webhook event types and event structures after an upgrade.
How do you install this skill?
- The “latest” API version is time-sensitive and should be rechecked against the current official changelog and upgrade guide before use.
- The examples contain Stripe key placeholders but do not explain production secret storage, rotation, or log redaction.
- The guide recommends testing and staged adoption without defining acceptance criteria, rollback steps, or codebase-specific migration verification.
- It does not address reachability of Stripe documentation, APIs, or related CDNs from mainland-China networks or provide alternatives.
- Shell / CLI
- Network access
The repository contains 24 skills. Following the README's manual installation method, run this in your project: npx skills add https://docs.stripe.com. Manually installed skills do not auto-update; run npx skills update -y. The README does not provide a command for installing only upgrade-stripe.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/stripe/ai.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/skills/upgrade-stripe" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Once installed, send your agent any of these to trigger it:
- Upgrade my Stripe integration to 2026-06-24.dahlia and list the SDK, Stripe.js, and webhook changes I should check.
Place the skill at skills/upgrade-stripe/SKILL.md in a compatible Agent Skills client, then make a specific request such as: “Upgrade my Stripe integration to 2026-06-24.dahlia and list the SDK, Stripe.js, and webhook changes I should check.”
What are this skill's strengths and limitations?
- Covers the API, server-side SDKs, Stripe.js, and mobile SDKs in one guide.
- Explains different upgrade strategies for dynamically typed and strongly typed languages.
- Includes a concrete upgrade checklist and Stripe-Version testing examples.
- Calls out unfamiliar webhook events, event structure changes, and object IDs up to 255 characters.
- It is guidance rather than an automated migration tool or test suite.
- It does not provide product-by-product migration instructions for specific changes.
- There is no documented installation command for this individual skill.
- Language and platform examples are limited, so support for other environments is not established by the source.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Stripe Version Upgrade Guide this page | 50 · Use with care | ★ 1.9k | 11d ago | MIT |
| Stripe Integration Best Practices | 53 · Use with care | ★ 1.9k | 11d ago | MIT |
| PinMe UniwebPay Payment Integration | 60 · Recommended | ★ 3.7k | 3mo ago | MIT |
| Azure API Center for .NET ✓ Microsoft · Official | 48 · Use with care | ★ 2.7k | 3mo ago | MIT |
| Google Mobile Ads Interstitial Integration Guide ✓ Google · Official | 41 · Not recommended | ★ 21k | 11d ago | Apache-2.0 |
How did FollowSkills review this skill?
The content is primarily upgrade guidance and code examples, with no apparent malware, covert exfiltration, or destructive defaults; examples use test-key placeholders and recommend explicit API versions. However, it does not explain secret management, sensitive-data flows, user confirmation, rollback, or dependency security, so points are deducted.
The guide is internally organized and covers API versions, server SDKs, Stripe.js, mobile SDKs, and a checklist. It lacks skill-specific tests, a compatibility matrix, abnormal-input handling, and diagnostic failure guidance. With only static evidence and no reproducible execution evidence, the score remains conservative.
The audience and common scenarios are reasonably clear, covering several Stripe client categories and staged upgrades. Inputs, outputs, trigger conditions, non-fit boundaries, Chinese-language support, and mainland-China network reachability are not specified, so points are deducted.
The document is readable and includes layered explanations, examples, upgrade steps, official documentation links, and repository-level MIT licensing, synchronization, and security-reporting context. It lacks skill-specific installation notes, changelog, explicit maintenance ownership, version governance, and troubleshooting; publisher identity is unverified.
The checklist and version-configuration examples can directly support common upgrade work and include practical webhook, test-header, and object-ID reminders. They do not analyze a user's concrete codebase, verify migration results, or provide a complete rollback procedure; static evidence therefore supports only a conservative score.
The guide links to auditable first-party Stripe changelog, upgrade, SDK, and mobile documentation, and the repository has general CI. There are no skill-specific tests or third-party execution records covering the key paths, so conclusions rely mainly on documentation claims and receive a limited score.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →