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 identifies the domain (Stripe payment processing), lists specific capabilities (checkout, subscriptions, webhooks), and provides explicit trigger guidance via a 'Use when...' clause. It uses proper third-person voice and includes natural keywords developers would use when seeking this functionality.
| 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 checkout, subscriptions, webhooks) and 'when' (explicit '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-specific payment processing with distinct triggers like 'Stripe', 'PCI-compliant', 'webhooks', 'subscriptions'. Unlikely to conflict with general 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 a broad range of Stripe integration patterns, which is its primary strength. However, it is excessively verbose—much of the conceptual explanation (payment flow types, subscription components, customer management basics) is unnecessary for Claude. The monolithic structure with no progressive disclosure or external references makes it a poor use of context window budget.
Suggestions
Remove or drastically reduce the 'Core Concepts', 'When to Use This Skill', and 'Customer Management' explanatory sections—Claude already understands these concepts. Keep only non-obvious Stripe-specific guidance (e.g., Checkout Sessions vs Payment Intents tradeoffs).
Split into multiple files: keep SKILL.md as a concise overview with Quick Start and Pattern 1, then reference separate files like WEBHOOKS.md, SUBSCRIPTIONS.md, TESTING.md for detailed patterns.
Add an explicit end-to-end integration workflow with validation steps (e.g., 1. Set up test keys → 2. Implement checkout → 3. Verify webhook endpoint with Stripe CLI → 4. Test with test cards → 5. Switch to live keys).
Remove the manual webhook signature verification function—Stripe's SDK already handles this via `construct_event`, and showing both is redundant and potentially confusing.
| 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; basic error handling patterns). The 'Core Concepts' section is largely unnecessary catalog-style information. The 'When to Use This Skill' section lists obvious use cases. Multiple patterns could be consolidated significantly. | 1 / 3 |
Actionability | The code examples are concrete, executable, and copy-paste ready across Python and JavaScript. Patterns cover checkout sessions, Payment Intents, subscriptions, webhooks, refunds, customer management, and testing with specific test card numbers. | 3 / 3 |
Workflow Clarity | Individual patterns are clear, but there's no explicit end-to-end workflow showing how the pieces connect (e.g., create customer → create subscription → handle webhook → verify). The webhook section includes idempotency handling which is good, but there are no validation checkpoints or feedback loops for the overall integration process (e.g., verifying webhook connectivity, testing in test mode before going live). | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no references to external files and no bundle files. All content—quick start, 5 patterns, webhooks, customer management, refunds, testing—is inlined in a single massive file. Content like webhook best practices, customer management, and refund handling could easily be split into separate referenced files. | 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
34632bc
- 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.