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

82%

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

Quality

Content

65%

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 complete, executable Stripe code, but it is overly verbose and monolithic: generic instruction boilerplate and all implementation detail live inline while the referenced bundle files do not exist. Workflow guidance lacks sequenced validation checkpoints for risky payment operations.

Suggestions

Move the detailed pattern code (webhooks, customer management, refunds, testing) into the referenced files and keep SKILL.md as a concise overview, or remove the Resources section if those files will not be created.

Replace the generic "Instructions" and "Do not use this skill when" boilerplate with a concrete end-to-end Stripe integration sequence that includes explicit validation checkpoints (e.g., test-card verification before production, webhook signature verification, idempotency checks).

Trim filler phrases such as "robust" and "Apply relevant best practices and validate outcomes" so every line adds Stripe-specific value Claude would not already know.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable code rather than concept prose, but it pads ~450 lines with generic boilerplate ("Clarify goals, constraints, and required inputs", "Apply relevant best practices and validate outcomes") and inline detail that belongs in referenced files; it is not lean enough for anchor 3 but avoids anchor 1's concept-explaining verbosity.	2 / 3
Actionability	Code blocks are fully executable and copy-paste ready across checkout sessions, payment intents, subscriptions, webhooks, customer management, refunds, and testing, matching the anchor for specific executable examples.	3 / 3
Workflow Clarity	Content is organized by topic rather than as a sequenced integration workflow, and the "Instructions" section is vague filler; a Testing section provides some validation but there are no explicit validate-fix-retry checkpoints for risky payment/refund operations, capping it at 2 per the rubric guideline.	2 / 3
Progressive Disclosure	Sections are clearly organized (not the monolithic wall of anchor 1), but all detail is inline and the "Resources" section lists 8 bundle files (references/ and assets/) that do not exist, so content that should be separate stays inline against broken references.	2 / 3
	Total	9 / 12 Passed

Description

100%

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 cleanly answers both what the skill does and when to use it, with concrete capability lists and natural trigger terms scoped to a distinct Stripe niche. Minor buzzword padding ("robust") does not materially weaken it.

Dimension	Reasoning	Score
Specificity	"Implement Stripe payment processing...including checkout, subscriptions, and webhooks" lists multiple concrete capabilities (checkout, subscriptions, webhooks), matching the anchor for several specific actions; the lone buzzword "robust" does not reduce it to anchor 2's incomplete coverage.	3 / 3
Completeness	It states both what ("Implement Stripe payment processing...including checkout, subscriptions, and webhooks") and when ("Use when integrating Stripe payments...") with an explicit trigger clause, so it is not capped at 2.	3 / 3
Trigger Term Quality	"Use when integrating Stripe payments, building subscription systems, or implementing secure checkout flows" uses natural phrasing a user would say, with good coverage of common variants rather than just technical jargon.	3 / 3
Distinctiveness Conflict Risk	"Stripe payment processing" is a clear, narrowly-scoped niche with distinct triggers unlikely to fire for unrelated skills, rather than a generic domain that would overlap with others.	3 / 3
	Total	12 / 12 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: e63f7dd

Reviewed: about 24 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.