payment-gateway-integration
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.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill payment-gateway-integration92
Does it follow best practices?
Validation for skill structure
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, includes natural trigger terms users would actually say, explicitly states both what it 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, actionable skill with excellent code examples and good token efficiency. The main weakness is the lack of explicit workflow sequencing for implementing payment processing end-to-end, particularly missing validation checkpoints for testing webhooks and verifying sandbox behavior before production deployment.
Suggestions
Add a numbered implementation workflow with validation steps (e.g., '1. Set up sandbox credentials, 2. Test payment intent creation, 3. Verify webhook delivery in Stripe dashboard, 4. Test refund flow, 5. Switch to production keys')
Include explicit verification step for webhook setup: 'Use Stripe CLI to test webhooks locally: stripe listen --forward-to localhost:3000/webhooks/stripe'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing executable code without explaining what Stripe or webhooks are. Every section delivers actionable content without padding or unnecessary context. | 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 methods. | 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 deployment'. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections. PayPal details appropriately delegated to a reference file with clear signaling of what's covered there. Main file stays focused on Stripe while acknowledging other providers. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 Passed | |
- 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.