CtrlK
BlogDocsLog inGet started
Tessl Logo

upgrade-stripe

Guide for upgrading Stripe API versions and SDKs

72

1.51x
Quality

58%

Does it follow best practices?

Impact

100%

1.51x

Average score across 3 eval scenarios

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

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

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

SKILL.md
Quality
Evals
Security

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 well-structured and highly actionable with broad executable examples and a clear upgrade checklist, but it carries some over-explanation of basic concepts and pervasive inline version numbers that slightly hurt token efficiency.

Suggestions

Trim explanations of well-known concepts (e.g., the semantic-versioning MAJOR.MINOR.PATCH breakdown and the backward/breaking change definitions) to assume Claude's competence.

Move volatile version strings (2026-07-29.dahlia, 2025-08-27.basil, etc.) into a single 'Current target version' note rather than repeating them across examples.

Add an explicit validate-fix-retry loop after the test step in the Upgrade Checklist (e.g., 'If tests fail, review changelog breaking changes, fix, and re-test').

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete code, but explains concepts Claude already knows (semantic versioning MAJOR.MINOR.PATCH, backward-vs-breaking change definitions) and inlines time-sensitive version numbers throughout rather than isolating them, which warrants tightening.

3 / 5

Actionability

Executable copy-paste code spans Python, Ruby, Node.js, and curl, plus concrete package commands ('npm update stripe', 'pip install --upgrade stripe'), with only minor high-level gaps such as 'Update webhook handlers to handle new event structures'.

4 / 5

Workflow Clarity

A 9-step Upgrade Checklist gives a clear sequence and includes a verification checkpoint (test against the new version via the Stripe-Version header), though an explicit fix-and-retest feedback loop is not spelled out.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections with one-level-deep external doc links ('See [SDK Version Management](...)'), and no bundle files exist to require further splitting; only minor organization gaps remain.

4 / 5

Total

15

/

20

Passed

Description

48%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 names a clear, distinct niche but is thin on specifics and lacks any explicit trigger ('Use when') guidance, capping completeness and trigger quality at the midpoint.

Suggestions

Add concrete actions beyond 'upgrading', e.g. 'Upgrade Stripe API versions, server-side SDKs, Stripe.js, and mobile SDKs'.

Append an explicit trigger clause such as 'Use when the user asks to upgrade or migrate Stripe API versions or SDKs'.

Include natural synonyms like 'migrate', 'update', or 'bump version' to broaden trigger coverage.

DimensionReasoningScore

Specificity

The phrase 'Guide for upgrading Stripe API versions and SDKs' names the domain (Stripe API versions, SDKs) but the action is a single generic verb ('upgrading'), so coverage of concrete actions is minimal rather than comprehensive.

2 / 5

Completeness

It clearly states what the skill does ('Guide for upgrading Stripe API versions and SDKs') but provides no explicit 'Use when...' trigger guidance; per the rubric a missing when-clause caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like 'upgrading', 'Stripe', 'API versions', and 'SDKs' are relevant and somewhat natural, but common variations or synonyms a user might say (e.g., 'migrate', 'update Stripe', 'bump version') are missing.

3 / 5

Distinctiveness Conflict Risk

The Stripe-version-upgrade niche is clearly distinct from most skills, with only minor overlap risk against a broad generic Stripe integration skill.

4 / 5

Total

12

/

20

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
stripe/ai
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.