Integrates payment processing with Stripe, PayPal, or Square including subscriptions, webhooks, and PCI compliance. Use when implementing checkout flows, recurring billing, or handling refunds and disputes.
96
93%
Does it follow best practices?
Impact
100%
1.25xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
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 well-crafted skill description that excels across all dimensions. It provides specific capabilities, uses natural trigger terms that users would actually say, explicitly states both what the skill does and when to use it, and has a clear distinctive niche in payment processing that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'payment processing', 'subscriptions', 'webhooks', 'PCI compliance', 'checkout flows', 'recurring billing', 'refunds and disputes'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Integrates payment processing with Stripe, PayPal, or Square including subscriptions, webhooks, and PCI compliance') and when ('Use when implementing checkout flows, recurring billing, or handling refunds and disputes'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Stripe', 'PayPal', 'Square', 'checkout', 'billing', 'refunds', 'disputes', 'subscriptions', 'webhooks'. Good coverage of payment-related terms users naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on payment processing with specific platform names (Stripe, PayPal, Square) and payment-specific terminology. Unlikely to conflict with other skills due to distinct domain focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong skill with excellent executable code examples and efficient token usage. The Stripe integration is comprehensive and actionable, with proper webhook handling included. The main weakness is the lack of an explicit implementation workflow with validation checkpoints for what is inherently a multi-step, high-stakes integration process.
Suggestions
Add an explicit implementation workflow section with numbered steps (e.g., '1. Set up sandbox account, 2. Implement payment intent, 3. Test webhook locally with Stripe CLI, 4. Verify signature validation works, 5. Deploy to staging...')
Include validation checkpoints such as 'Verify webhook endpoint returns 200 before enabling in Stripe dashboard' and 'Test refund flow in sandbox before production'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing executable code without explaining what payment gateways are or how Stripe works conceptually. Every section delivers actionable content without padding. | 3 / 3 |
Actionability | Provides fully executable JavaScript code for payment intents, subscriptions, refunds, and webhook handling. The code is copy-paste ready with proper error handling and real SDK usage. | 3 / 3 |
Workflow Clarity | While individual operations are clear, there's no explicit workflow sequence for implementing a complete payment flow. Missing validation checkpoints like 'verify webhook is working before going live' or 'test refund flow before production'. The security checklist helps but lacks a clear implementation order. | 2 / 3 |
Progressive Disclosure | Excellent structure with Stripe as the primary example inline, PayPal appropriately referenced to a separate file, and clear sections for webhooks, security, and best practices. One-level-deep reference is well-signaled. | 3 / 3 |
Total | 11 / 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.
90d6bd7
Table of Contents
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.