stripe-integration-expert

Production-grade Stripe integrations: subscriptions with trials and proration, one-time payments, usage-based billing, checkout sessions, idempotent webhook handlers, customer portal, and invoicing. Covers Next.js, Express, and Django patterns. Use when integrating Stripe for the first time, debugging webhook reliability issues, migrating from a different payment provider, or adding usage-based billing to an existing subscription product.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./engineering-team/skills/stripe-integration-expert/SKILL.md

Quality

Content

61%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.

A code-rich, actionable reference for Stripe integrations that assumes Claude's competence and provides copy-paste patterns, but it is monolithic with no progressive disclosure to bundle files and lacks an overall sequenced workflow with validation checkpoints.

Suggestions

Split large reference blocks (e.g., the full webhook handler, plan-change logic, CLI testing) into files under references/ and link to them from SKILL.md so the top-level file stays an overview.

Replace the placeholder 'name: "username-undefined"' and move the time-sensitive apiVersion pin into a clearly labeled/deprecated section or a config note so it does not stale the skill.

Add an explicit end-to-end workflow with validation checkpoints (e.g., configure -> test locally with stripe listen -> verify idempotency table -> deploy) to sequence the multi-step integration process.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, executable TypeScript with almost no explanatory padding of concepts Claude already knows, but it carries a time-sensitive apiVersion pin ('2024-04-10') outside any deprecated section and a leftover placeholder ('name: "username-undefined"') that could be trimmed.	4 / 5
Actionability	Copy-paste-ready code covers the common cases (checkout, plan changes, webhooks, usage billing, portal, CLI testing, feature gating), but app-specific helpers (getAuthUser, db, sendDunningEmail) are undefined and the placeholder name value is a minor gap.	4 / 5
Workflow Clarity	The webhook handler shows a clear sequence with validation (signature verification, idempotency check, 500-retry on failure), but the skill as a whole is a sectioned code catalog without a unified multi-step workflow or explicit checkpoints across operations.	3 / 5
Progressive Disclosure	Roughly 477 lines are fully inlined with no bundle files or external references; large reference-style content such as the complete webhook handler that clearly belongs in separate files is monolithic, with no one-level-deep reference structure to navigate.	2 / 5
	Total	13 / 20 Passed

Description

92%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.

A strong, specific description that clearly states what the skill does and when to use it with natural trigger phrases. Only minor keyword-synonym coverage keeps trigger term quality from a perfect score.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'subscriptions with trials and proration, one-time payments, usage-based billing, checkout sessions, idempotent webhook handlers, customer portal, and invoicing' — giving comprehensive coverage rather than vague language.	5 / 5
Completeness	Explicitly answers both 'what' (the integration capabilities listed) and 'when' via a concrete 'Use when ...' clause with multiple trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'integrating Stripe for the first time', 'debugging webhook reliability issues', 'migrating from a different payment provider', and 'adding usage-based billing' read as things users would actually say, though a few synonyms (e.g., 'payment gateway', 'Stripe webhooks') are missing.	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to Stripe integrations with Stripe-specific triggers, giving it a clear niche and minimal overlap risk with other skills.	5 / 5
	Total	19 / 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: alirezarezvani/claude-skills
Path: engineering-team/skills/stripe-integration-expert/SKILL.md
Commit: 19392f7

Reviewed: ~7 hours 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.