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

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/stripe-integration/SKILL.md

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.

The body is a thorough, largely executable Stripe cookbook with good code coverage, but it is padded with concept explanations Claude already knows, lacks an explicit end-to-end workflow with validation feedback loops, and promises reference/asset files that are not present. Tightening concept prose, realising the referenced bundle files, and adding a sequenced integration checklist would lift the weaker dimensions.

Suggestions

Remove or shrink the 'Core Concepts' section explanations of Stripe basics (Checkout Session, Payment Intent, Product/Price/Subscription/Invoice) that Claude already knows, keeping only non-obvious guidance.

Create the referenced bundle files (references/*.md, assets/*.py) and move the bulk of the inlined pattern code into them, leaving SKILL.md as a concise overview with one-level-deep links.

Add an explicit end-to-end integration workflow with validation checkpoints (configure webhooks → verify signature → test with test cards → confirm idempotent handling → monitor) including a validate→fix→retry loop for refunds and disputes.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable code, but the 'Core Concepts' section explains Stripe basics Claude already knows (what a Checkout Session, Payment Intent, Product, Price, Subscription, and Invoice are) and several padded bullet annotations ('Minimal PCI compliance burden', 'Fastest implementation') could be trimmed, fitting the 3 anchor rather than 2 because the bulk is useful code.	3 / 5
Actionability	Provides copy-paste-ready executable code across checkout, payment intents, subscriptions, webhooks, customers, refunds, and testing, but the 'Webhook Best Practices' idempotency example relies on undefined stubs (is_event_processed, mark_event_processed, log_error), a minor gap that keeps it just below the 5 anchor.	4 / 5
Workflow Clarity	The content is organized as a pattern catalog rather than a sequenced integration workflow; webhook handling includes signature validation, but there are no explicit validate→fix→retry feedback loops for destructive/batch operations like refunds and disputes, which per the rubric caps workflow_clarity at 3.	3 / 5
Progressive Disclosure	Section headers and a signaled 'Resources' list provide some structure, but all detailed code is inlined in SKILL.md instead of split into the referenced files, and the referenced bundle paths (references/.md, assets/.py) do not actually exist, fitting the 3 anchor where content that should be separate is inline and references are not fully realized.	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.

The description is strong: third-person voice, explicit 'Use when' triggers, concrete capabilities, and a clearly distinct Stripe niche. The main weakness is slight under-coverage of the skill's full scope (refunds, disputes, customer management) and a few missing synonyms.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('checkout, subscriptions, and webhooks', 'integrating Stripe payments', 'building subscription systems', 'secure checkout flows'), but omits capabilities the skill actually covers such as refunds, disputes, and customer management, leaving minor gaps that keep it below the comprehensive 5 anchor.	4 / 5
Completeness	Explicitly answers both what ('Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks') and when ('Use when integrating Stripe payments, building subscription systems, or implementing secure checkout flows') with concrete trigger phrases, matching the 5 anchor.	5 / 5
Trigger Term Quality	Good coverage of natural phrases users would say ('Stripe payments', 'checkout', 'subscriptions', 'subscription systems', 'secure checkout flows'), but missing common synonyms like 'billing' and 'recurring payments', so it falls short of the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	The Stripe-specific niche and concrete Stripe trigger terms make it clearly distinguishable from other payment/general skills with minimal conflict risk, matching the 5 anchor.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 8 missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/stripe-integration/SKILL.md
Commit: 3eff4af

Reviewed: 1 day 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.