upgrade-stripe

Guide for upgrading Stripe API versions and SDKs

1.51x

Quality

60%

Does it follow best practices?

Impact

100%

1.51x

Average score across 3 eval scenarios

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugins/stripe/skills/upgrade-stripe/SKILL.md

The canonical home for this skill is upgrade-stripe in stripe/ai

Quality

Content

67%Weight 40%Scale 1-5

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

The body is a well-structured, actionable guide with executable code and a clear upgrade checklist including testing checkpoints. Its main weaknesses are inline time-sensitive version pins that will age poorly and a few vague checklist steps (webhook updates) that lack concrete examples.

Suggestions

Move the pinned 'latest' API version statement into a clearly labeled section (e.g. 'Current versions') or instruct Claude to check the changelog for the latest version instead, so the skill does not silently go out of date.

Add a concrete example or reference for the vague checklist step 'Update webhook handlers to handle new event structures', such as a skeleton webhook handler that safely ignores unfamiliar event types.

Add an explicit feedback loop after the testing step, e.g. 'If tests fail, review the changelog entry for the failing endpoint, adjust code, and re-test with the Stripe-Version header before committing.'

Dimension	Reasoning	Score
Conciseness	The body is dense and mostly Stripe-specific rather than generic knowledge Claude already has, but time-sensitive version pins ('The latest Stripe API version is 2026-07-29.dahlia', dated examples throughout) appear inline rather than in a deprecated/old-patterns section, which the guidelines penalize. A few sections (the backward/ breaking change lists) could also be tightened — matching anchor 3, not 4.	3 / 5
Actionability	Concrete, executable snippets in Python, Ruby, JavaScript, and bash (curl with the Stripe-Version header) plus an upgrade checklist with real commands ('npm update stripe', 'pip install --upgrade stripe'). Minor gaps remain — 'Update webhook handlers to handle new event structures' gives no concrete example — matching anchor 4 rather than 5.	4 / 5
Workflow Clarity	The numbered 'Upgrade Checklist' provides a clear sequence, and validation checkpoints are present ('Test your integration against the new API version using the Stripe-Version header', 'Test webhooks with the new version structure before upgrading'). It falls short of anchor 5 because there is no explicit feedback loop for what to do when tests fail.	4 / 5
Progressive Disclosure	The skill is a single SKILL.md with well-organized sections and clearly signaled one-level-deep links to Stripe's official docs ('See [SDK Version Management](https://docs.stripe.com/sdks/set-version.md) for details'). No bundle files exist to split content into, but some inline detail (full mobile-SDK versioning section) could live in reference files — matching anchor 4 rather than 5.	4 / 5
	Total	15 / 20 Passed

Description

52%Weight 40%Scale 1-5

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 is distinct and unambiguous about its niche but under-sells the skill: it gives only a generic single-verb action and entirely omits 'when to use' trigger guidance. Adding an explicit 'Use when...' clause and 1-2 more concrete actions would materially improve it.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions upgrading or migrating Stripe integrations, changing the API version, or updating stripe, stripe-java, stripe-ios, stripe-android, or @stripe/stripe-js packages.'

Name 1-2 concrete actions in the description, e.g. 'Update the apiVersion in server-side SDK initialization, review the API changelog for breaking changes, and migrate Stripe.js and mobile SDKs.'

Include natural synonyms users would say — 'migrate', 'update Stripe SDK', 'apiVersion' — to strengthen trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain clearly ('upgrading Stripe API versions and SDKs') but the action set is minimal and generic — a single verb 'upgrading' with no listing of concrete actions like migrating SDKs or updating the apiVersion parameter. It matches anchor 2 ('Processes PDF files'): domain named, actions minimal.	2 / 5
Completeness	The 'what' is clear (a guide for upgrading Stripe API versions and SDKs) but there is no 'when' — no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Terms like 'upgrading', 'Stripe', 'API versions', and 'SDKs' are phrases users would naturally say, but common variations are missing — no 'migrate', 'Stripe.js', 'mobile SDK', or 'apiVersion'. This matches anchor 3 ('Works with PDF files'): some relevant keywords, missing common variations.	3 / 5
Distinctiveness Conflict Risk	The description names a specific vendor (Stripe) and a specific operation (version/SDK upgrades), forming a clear niche with minimal conflict risk — it is unlikely to trigger for the wrong skill. This matches anchor 5; no closely related skill plausibly overlaps.	5 / 5
	Total	13 / 20 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: openai/plugins
Path: plugins/stripe/skills/upgrade-stripe/SKILL.md
Commit: 5fd93af

Reviewed: 2 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.