CtrlK
BlogDocsLog inGet started
Tessl Logo

upgrade-stripe

Guide for upgrading Stripe API versions and SDKs

55

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

72%

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 concrete multi-language code and a clear upgrade checklist, and is well-structured as a standalone overview. It loses points for explaining background concepts Claude already knows and for lacking explicit validation checkpoints in the upgrade workflow.

Suggestions

Trim background explanations Claude already knows (date-based versioning rationale, MAJOR/MINOR/PATCH semantics, backward-vs-breaking definitions) to tighten token use.

Add explicit validation checkpoints to the upgrade checklist, e.g. after setting the API version verify a sample request returns the expected response shape, and confirm webhook signature verification before going live.

Reduce repetition of the literal version string 2026-02-25.clover by defining the target version once and referencing it.

DimensionReasoningScore

Conciseness

The body is mostly efficient with focused sections and tight code, but it explains concepts Claude already knows (date-based versioning, semantic-versioning semantics, backward vs breaking changes) and repeats the version string many times, so it could be tightened.

2 / 3

Actionability

It provides concrete executable code across Python/Ruby/Node, an explicit curl example with the Stripe-Version header, copy-paste package commands, and a numbered upgrade checklist — fully actionable guidance.

3 / 3

Workflow Clarity

The Upgrade Checklist gives a clear 9-step sequence with testing guidance, but it lacks validation checkpoints or feedback loops for an operation that reconfigures a production integration, capping workflow clarity at 2.

2 / 3

Progressive Disclosure

It is a single self-contained file with well-organized sections and an overview; the only links are external Stripe docs (not nested local bundle chains), so navigation is clear and one level deep.

3 / 3

Total

10

/

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 correctly identifies the Stripe upgrade domain but stops short of listing concrete actions and provides no explicit use-trigger. It is clear but generic enough to benefit from trigger terms and a "Use when" clause.

Suggestions

Add a "Use when..." clause naming explicit triggers, e.g. "Use when upgrading Stripe API versions, migrating SDKs, or updating Stripe.js/mobile SDKs."

List concrete actions to raise specificity, e.g. "Updates the API version, bumps server-side SDK packages, pins Stripe.js, and refreshes mobile SDK versions."

Include natural trigger variations users actually say — "upgrade Stripe", "migrate Stripe API", "bump Stripe SDK" — alongside version-date references.

DimensionReasoningScore

Specificity

"Guide for upgrading Stripe API versions and SDKs" names the domain and the upgrade action but does not list multiple concrete sub-actions, matching the anchor that names domain and some actions without being comprehensive.

2 / 3

Completeness

It states what the skill does but provides no "Use when..." clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 2.

2 / 3

Trigger Term Quality

It includes relevant terms like "Stripe API versions and SDKs" a user might say, but omits common variations such as "upgrade", "migrate", "Stripe.js", or version dates, so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

It is scoped to Stripe version/SDK upgrades, a fairly clear niche, but the thin trigger vocabulary means it could still overlap with adjacent Stripe skills rather than being unmistakably distinct.

2 / 3

Total

8

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
Reviewed

Table of Contents

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.