CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

stripe-integration

Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks. Use when integrating Stripe payments, building subscription systems, or implementing secure checkout flows.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

57%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 genuinely useful, code-heavy Stripe integration reference with real API usage, but it reads as a monolithic pattern dump: no sequenced workflow with validation checkpoints, no progressive disclosure into reference files, and several filler sections that assume too little of Claude. Strong execution detail undermined by organization and padding.

Suggestions

Add an ordered integration workflow with validation checkpoints (e.g., 1. create product/price → 2. create checkout session → 3. register and verify webhook endpoint → 4. test with test cards before going live) so the patterns hang off a clear sequence.

Split the bulk into one-level-deep reference files (e.g., WEBHOOKS.md, SUBSCRIPTIONS.md, TESTING.md) and keep SKILL.md as a concise overview with well-signaled links, instead of inlining ~440 lines.

Delete the generic filler sections ("Instructions", "Do not use this skill when", "Use this skill when") and the Core Concepts explanations of Stripe basics Claude already knows, replacing stub comments in webhook handlers with minimal complete implementations.

DimensionReasoningScore

Conciseness

The bulk is dense, useful Stripe pattern code, but it is padded with sections Claude does not need: a generic "Instructions" list ("Clarify goals, constraints, and required inputs"), a "Use this skill when" list duplicating the description, and Core Concepts explaining basics Claude already knows ("Product: What you're selling", "Price: How much and how often").

3 / 5

Actionability

Concrete, executable Python throughout — checkout sessions, payment intents, subscriptions, customer portal, a signature-verified webhook endpoint, refunds, and test cards. Falls short of fully copy-paste ready because webhook handler bodies are stubs ("# Update your database", "# Send confirmation email") and helper functions like is_event_processed are undefined.

4 / 5

Workflow Clarity

Organized as a pattern catalog rather than a sequenced integration workflow — there is no ordered path (create price → create session → verify webhook → test) with checkpoints tying steps together. Individual patterns do show validation (signature verification, idempotency, an assert in Testing), so it sits above a rough-sequence-only level.

3 / 5

Progressive Disclosure

Section headers are clear and navigable, but ~440 lines of pattern library (webhook handling, testing, refunds/disputes) are all inlined in SKILL.md with no reference files at all. Content that clearly belongs in separate reference files (e.g., WEBHOOKS.md, TESTING.md) is inline, though the decent structure keeps it above the minimal-structure anchor.

3 / 5

Total

13

/

20

Passed

Description

87%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 description that clearly states capabilities and explicit trigger conditions in third-person voice. Minor improvements possible by adding the refund/dispute/billing capabilities the skill actually covers.

DimensionReasoningScore

Specificity

Names the domain plus several concrete actions ("checkout, subscriptions, and webhooks"), though "robust, PCI-compliant" edges toward buzzword and capabilities covered in the body (refunds, disputes, payment-method management) are absent from the description.

4 / 5

Completeness

Explicitly answers both "what" ("Implement Stripe payment processing... including checkout, subscriptions, and webhooks") and "when" ("Use when integrating Stripe payments...") with concrete trigger phrases, matching the anchor-5 pattern.

5 / 5

Trigger Term Quality

"Use when integrating Stripe payments, building subscription systems, or implementing secure checkout flows" provides natural trigger phrases users would say. Missing common synonyms such as "billing", "payment gateway", or "refunds" keeps it below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche anchored specifically to Stripe with distinct triggers; only "secure checkout flows" offers mild generic overlap, and it is framed within Stripe payment integration.

5 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rmyndharis/antigravity-skills

Path

skills/stripe-integration/SKILL.md

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.