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.
68
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
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 strong skill description that clearly communicates specific capabilities (payment processing with named providers, subscriptions, webhooks, PCI compliance) and provides explicit trigger guidance via a 'Use when...' clause. It uses third person voice correctly, includes natural keywords developers would use, and occupies a distinct niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: 'payment processing with Stripe, PayPal, or Square', 'subscriptions', 'webhooks', 'PCI compliance', 'checkout flows', 'recurring billing', 'refunds and disputes'. | 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') with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Stripe', 'PayPal', 'Square', 'checkout flows', 'recurring billing', 'refunds', 'disputes', 'subscriptions', 'webhooks', 'PCI compliance' — these are all terms a developer would naturally use when seeking payment integration help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around payment processing and specific providers (Stripe, PayPal, Square). The trigger terms are domain-specific enough that this is unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides solid, executable Stripe integration code covering key use cases (payments, subscriptions, refunds, webhooks). However, it suffers from redundancy between the security checklist and best practices sections, lacks a clear end-to-end workflow with validation steps, and doesn't cover Square despite the skill description promising it. The PayPal reference file is missing from the bundle.
Suggestions
Merge the security checklist and best practices sections into a single concise section to eliminate redundancy
Add an end-to-end integration workflow with numbered steps and validation checkpoints (e.g., 1. Set up Stripe account, 2. Configure webhook endpoint, 3. Test with `stripe listen --forward-to`, 4. Verify events received, 5. Deploy)
Either add Square integration content or remove it from the skill's scope/description
Provide the referenced paypal-integration.md bundle file to support the progressive disclosure reference
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The security checklist and best practices sections overlap significantly (both mention webhook signatures, official SDKs, sandbox testing, not storing card data). The Do/Don't section largely restates the checklist. Otherwise the code examples are reasonably lean. | 2 / 3 |
Actionability | Provides fully executable Node.js code for Stripe payment intents, subscriptions, refunds, and webhook handling. The code is copy-paste ready with concrete API calls and proper patterns like cents conversion and signature verification. | 3 / 3 |
Workflow Clarity | The skill presents individual components (payment intent, subscription, webhook) but lacks a clear end-to-end workflow sequence showing how these pieces connect. There are no explicit validation checkpoints or feedback loops for the integration process (e.g., verify webhook endpoint is registered, test with Stripe CLI before deploying). | 2 / 3 |
Progressive Disclosure | References PayPal integration in a separate file which is good structure, but the bundle has no files so the reference is unverifiable. Square integration mentioned in the description is entirely absent. The inline content could benefit from separating the security/best-practices into a reference file to keep the main skill leaner. | 2 / 3 |
Total | 9 / 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
- secondsky/claude-skills
- Commit
5e92b71
- 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.