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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, lean reference skill with executable examples and a clean one-level reference into references/details.md. Its main weakness is workflow clarity: critical/risky flows like webhook handling are presented as event lists in the body rather than as an explicit sequenced workflow with validation checkpoints.

Suggestions

Add a short sequenced webhook-implementation workflow in the body (receive -> verify signature -> handle idempotently -> respond) with an explicit validation checkpoint, rather than only listing event types.

Collapse the Subscriptions components gloss (Product/Price/Subscription/Invoice one-liners) since Claude already knows these basics, or move them into references/details.md.

Surface the test-card success/decline assertions as an explicit verify step so the testing section reads as a feedback loop rather than a single happy-path assertion.

Dimension	Reasoning	Score
Conciseness	The body is lean and decision-oriented (e.g., "Lower integration and maintenance burden than Payment Intents") with executable code and no boilerplate explaining what Stripe or a library is; the only mild glosses are one-line concept definitions kept minimal, so it stays at the efficient anchor rather than the 'mostly efficient but could be tightened' level.	3 / 3
Actionability	Provides fully executable code in Quick Start (a complete checkout Session.create call) and Testing (concrete test card numbers and a runnable test_payment_flow), making it copy-paste ready rather than pseudocode or abstract direction.	3 / 3
Workflow Clarity	Content is organized as a concepts catalog plus snippets rather than a sequenced multi-step workflow, and for a risky financial operation (webhooks) the body only lists event types without a verify-signature/idempotency checkpoint sequence (those details are deferred to references), which caps it at level 2 per the destructive/risky-operations guideline.	2 / 3
Progressive Disclosure	The SKILL.md is a clear overview with a single, well-signaled one-level-deep pointer to the real file references/details.md ("Read that file when the navigation tier above is insufficient"), with content appropriately split rather than monolithic.	3 / 3
	Total	11 / 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.

A strong, well-formed description: third-person voice, concrete capabilities, and an explicit 'Use when' trigger clause covering natural user phrasings. It is specific to the Stripe payments niche with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — "checkout, subscriptions, and webhooks" under "Implement Stripe payment processing" — rather than vague language, matching the anchor for listing several specific actions.	3 / 3
Completeness	It explicitly states both what it does ("Implement Stripe payment processing... including checkout, subscriptions, and webhooks") and when to use it ("Use when integrating Stripe payments, building subscription systems, or implementing secure checkout flows"), with an explicit trigger clause.	3 / 3
Trigger Term Quality	"Use when integrating Stripe payments, building subscription systems, or implementing secure checkout flows" supplies natural terms a user would actually say; it is above level 2 because it covers multiple common phrasings rather than a single keyword.	3 / 3
Distinctiveness Conflict Risk	The Stripe-specific niche and concrete triggers make it clearly distinguishable and unlikely to fire for an unrelated skill; it is not level 2 because the trigger set is tightly scoped to payments rather than overlapping generic document/file skills.	3 / 3
	Total	12 / 12 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: wshobson/agents
Commit: 5cc2549

Reviewed: 5 days 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.