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.
81
71%
Does it follow best practices?
Impact
97%
1.49xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/payment-processing/skills/stripe-integration/SKILL.mdQuality
Discovery
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.
This is a strong skill description that clearly communicates specific capabilities (checkout, subscriptions, webhooks), includes natural trigger terms users would say, and explicitly states both what the skill does and when to use it. The Stripe-specific focus makes it highly distinctive and unlikely to conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'checkout, subscriptions, and webhooks' along with 'PCI-compliant payment flows' and 'Stripe payment processing'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly 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'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Stripe', 'payments', 'checkout', 'subscriptions', 'webhooks', 'payment processing', 'subscription systems', 'secure checkout flows'. Good coverage of terms a developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Stripe specifically, with distinct triggers like 'Stripe payments', 'subscriptions', 'webhooks', and 'checkout flows'. Unlikely to conflict with generic coding skills or other payment provider skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, executable code examples covering the full breadth of Stripe integration patterns, which is its primary strength. However, it is far too verbose for a SKILL.md—it reads like a condensed version of Stripe's documentation rather than a focused skill file that assumes Claude's competence. The lack of progressive disclosure (everything in one file) and absence of a clear end-to-end workflow sequence significantly reduce its effectiveness as a skill.
Suggestions
Drastically reduce the 'Core Concepts' section—remove explanations of what Products, Prices, and Subscriptions are, and cut the webhook event list to just a brief mention that webhook verification is critical.
Split into multiple files: keep SKILL.md as a concise overview with Quick Start and pattern summaries, then reference separate files like WEBHOOKS.md, SUBSCRIPTIONS.md, CUSTOMER_MANAGEMENT.md for detailed code.
Add an explicit end-to-end integration workflow with numbered steps and validation checkpoints (e.g., 'verify webhook endpoint with Stripe CLI before going live', 'confirm test payment succeeds before deploying').
Remove the 'When to Use This Skill' section entirely—it restates the skill description and adds no actionable value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~350+ lines. It explains concepts Claude already knows (what Products, Prices, Subscriptions are; what customer management means), lists obvious webhook events, and includes lengthy code patterns that are essentially Stripe documentation repackaged. The 'Core Concepts' section is largely unnecessary padding. | 1 / 3 |
Actionability | The code examples are fully executable, copy-paste ready Python and JavaScript with proper error handling, real Stripe API calls, and concrete patterns covering checkout sessions, webhooks, subscriptions, refunds, and testing with test card numbers. | 3 / 3 |
Workflow Clarity | While individual patterns are clear, there's no explicit sequenced workflow tying the pieces together (e.g., 'first create customer, then set up webhook endpoint, then create checkout session'). The webhook section includes idempotency handling which is good, but there are no validation checkpoints for the overall integration flow or verification steps after deployment. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no references to external files. At this length, content like webhook handling, customer management, refund handling, and testing should be split into separate referenced files. Everything is inlined in one massive document with no navigation aids. | 1 / 3 |
Total | 7 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- wshobson/agents
- Commit
27a7ed9
- 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.