Name: upgrade-stripe
Rating: 63.470000000000006 (1 reviews)
Author: stripe

Blog Docs Log in Get started

upgrade-stripe

Guide for upgrading Stripe API versions and SDKs

1.21x

Quality

57%

Does it follow best practices?

Impact

95%

1.21x

Average score across 2 eval scenarios

Securityby

Risky

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./providers/claude/plugin/skills/upgrade-stripe/SKILL.md

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable, multi-language code and a clear upgrade checklist, but it mixes time-sensitive version numbers into the main flow and lacks an explicit validation feedback loop and any progressive file split. It is a strong, practical reference that could be tightened and re-structured.

Suggestions

Segregate time-sensitive version strings into a dedicated 'Current versions' or 'old patterns/deprecated' section so the main guidance stays evergreen.

Add an explicit validate-fix-retry loop to the upgrade checklist, e.g. 'Test with the Stripe-Version header; if handlers fail, fix and re-test before proceeding.'

Move the per-SDK versioning detail (server-side / Stripe.js / mobile) into separate reference files linked from a concise overview to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with code blocks, bullets, and doc links, but time-sensitive version strings (e.g. "2026-06-24.dahlia") are scattered inline rather than isolated in a deprecated/old-patterns section, which the guidelines say should penalize conciseness. Not level 1 (not padded with concepts Claude already knows) and not level 3 (time-sensitive info is not segregated).	2 / 3
Actionability	It provides fully executable, copy-paste-ready examples across languages (Python/Ruby/Node `stripe.api_version`/`apiVersion`), curl with the `Stripe-Version` header, and concrete package commands (`npm update stripe`, `pip install --upgrade stripe`). This matches the level-3 anchor of specific, executable, copy-paste-ready guidance.	3 / 3
Workflow Clarity	The "Upgrade Checklist" and "Migrating from v3" sections give a clear sequence and a testing step, but there is no explicit validate-then-fix-then-retry feedback loop, and an upgrade is a risky/batch-style operation the guidelines say should cap at 2 without such checkpoints. Not level 1 (steps are clearly sequenced) and not level 3 (no explicit validation feedback loop).	2 / 3
Progressive Disclosure	Sections are well-organized with clearly signaled external Stripe doc links, but the ~180-line skill is monolithic with no split reference files and detail (per-SDK versioning) is inline. No bundle files exist. Not level 1 (well structured, not a wall of text) and not level 3 (no one-level-deep internal reference split for a skill well over 50 lines).	2 / 3
	Total	9 / 12 Passed

Description

50%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly states the skill's purpose and domain but stops short of providing explicit activation triggers or comprehensive action coverage. It is competent yet generic enough to leave "when to use" only implied.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when upgrading Stripe API versions or SDKs, or when the user mentions Stripe version migration, Stripe.js major releases, or mobile SDK updates.'

Enumerate the concrete sub-actions the skill covers (server-side SDKs, Stripe.js, mobile SDKs, webhook handler updates) to raise specificity.

Include natural trigger variations like 'Stripe.js', 'mobile SDK', and 'API version migration' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Guide for upgrading Stripe API versions and SDKs" names the domain (Stripe API versions and SDKs) and one concrete action (upgrading), but does not list multiple specific actions. It is above level 1 because it identifies a concrete action and target, but below level 3 because it is not comprehensive across the upgrade sub-tasks.	2 / 3
Completeness	It answers "what" (a guide for upgrading Stripe API versions and SDKs) but "when" is only implied and there is no "Use when..." clause, which per the guidelines caps completeness at 2. Not level 1 because the what is clear; not level 3 because explicit trigger guidance is absent.	2 / 3
Trigger Term Quality	It includes relevant natural keywords ("upgrading", "Stripe", "API version", "SDKs") a user might say, but omits common variations (Stripe.js, mobile SDKs) and any trigger phrasing. Not level 1 (terms are natural, not jargon) and not level 3 (coverage is incomplete).	2 / 3
Distinctiveness Conflict Risk	The niche (Stripe version/SDK upgrades) is fairly specific and unlikely to trigger for unrelated skills, but without explicit triggers it could overlap with a general Stripe integration skill. Not level 1 (not generic) and not level 3 (no distinct explicit triggers).	2 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: stripe/ai
Commit: 61df611

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.