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 a comprehensive range of Stripe integration patterns, which is its primary strength. However, it is far too verbose—much of the conceptual explanation is unnecessary for Claude, and the monolithic structure with no progressive disclosure makes it a poor use of context window. The workflow lacks an overarching integration sequence with validation checkpoints.
Suggestions
Reduce the content by 60%+: remove the 'Core Concepts' and 'When to Use This Skill' sections entirely, and trim function docstrings that restate the obvious. Claude knows what a refund is.
Split into multiple files: keep SKILL.md as a concise overview with Quick Start, then reference separate files like WEBHOOKS.md, SUBSCRIPTIONS.md, CUSTOMER_MANAGEMENT.md, and TESTING.md.
Add an explicit integration workflow with validation steps: e.g., '1. Configure test keys → 2. Implement checkout → 3. Set up webhook endpoint → 4. Verify with `stripe listen --forward-to` → 5. Test end-to-end with test cards → 6. Switch to live keys'.
Remove Pattern 3 (Payment Intents with Elements) or reduce it to a one-line reference, since the skill already notes Pattern 2 is recommended—this would save significant tokens.
| 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), includes lengthy 'When to Use This Skill' and 'Core Concepts' sections that are largely unnecessary, and provides many patterns that could be condensed or referenced externally. The 'Customer Management' section explains basic CRUD operations Claude can easily derive. | 1 / 3 |
Actionability | The code examples are concrete, executable, and copy-paste ready across Python and JavaScript. Each pattern includes complete function definitions with error handling, proper imports, and realistic parameters. Test card numbers and test flow examples are practical and specific. | 3 / 3 |
Workflow Clarity | While individual patterns are clear, there's no explicit sequencing of the overall integration workflow (e.g., 'first set up webhooks, then implement checkout, then verify end-to-end'). The webhook section includes idempotency handling which is good, but there are no validation checkpoints for the overall integration process—no steps to verify webhook connectivity, test mode verification, or go-live checklist. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no references to external files. The extensive webhook handling, customer management, refund handling, and testing sections could each be separate referenced documents. Everything is inline, making the skill very long and difficult to navigate efficiently. | 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
91fe43e
- 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.