CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/payment-gateway-integration/skills/payment-gateway-integration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers concrete, executable Stripe and PayPal guidance with a genuinely useful one-level-deep reference file, but it is a recipe collection rather than a guided workflow: no sequenced steps, no validation checkpoints for money-moving operations, and noticeably duplicated checklist/Best Practices sections. Fixing the webhook async bug and covering (or dropping) Square would close the remaining gaps.

Suggestions

Merge the 'Security Checklist' and 'Best Practices' sections into one non-duplicated list, cutting items that restate PCI basics Claude already knows.

Add a short sequenced integration workflow with validation checkpoints (e.g. sandbox test → verify webhook signature and delivery → confirm payment succeeded before fulfilling the order), since payments are destructive/irreversible money operations.

Fix the Stripe webhook handler (mark the callback async, define/require the handlePaymentSuccess and handlePaymentFailed handlers), and either add a Square reference or remove Square from the description.

DimensionReasoningScore

Conciseness

The Stripe code is lean and API-specific (no padding, no explaining what Stripe is), but the "Security Checklist" and "Best Practices" sections largely duplicate each other ("Use official SDK only" vs "Use official SDK libraries", "Verify webhook signatures" vs "Verify all webhook signatures", "Test in sandbox first" vs "Test in sandbox environment"), and several Don'ts restate PCI basics Claude already knows. This is more than minor trimming, matching anchor 3 rather than 4.

3 / 5

Actionability

Provides concrete, near copy-paste-ready code: a PaymentService class with createPaymentIntent, createSubscription, and refund, plus a webhook handler using stripe.webhooks.constructEvent. Minor gaps keep it below anchor 5: the webhook callback uses 'await' inside a non-async function (a real bug), and Square — promised in the description — has no code or reference anywhere.

4 / 5

Workflow Clarity

The body is a set of recipes (service methods, webhook snippet, checklists) with no sequenced integration workflow or validation checkpoints — nothing like sandbox-test → verify webhook delivery → confirm payment before fulfilling. Payments are money-moving operations, so per the rubric's cap, missing validation/verification loops hold this at anchor 3 even though webhook signature checking is shown.

3 / 5

Progressive Disclosure

Verified against the actual bundle: references/paypal-integration.md exists, is well-signaled with a bullet list of its contents, and is one level deep (no nested references inside it). Structure is good but not anchor 5: the full Stripe implementation sits inline in SKILL.md while only PayPal is split out (an asymmetric split), and there is no Square reference despite the description naming it.

4 / 5

Total

14

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person, specific about providers and capabilities, with an explicit and well-phrased 'Use when' trigger clause. The only weakness is that the capability list leans on a single verb and a few natural synonyms (payment gateway, accept payments, invoices) are absent.

DimensionReasoningScore

Specificity

"Integrates payment processing with Stripe, PayPal, or Square including subscriptions, webhooks, and PCI compliance" names the domain and several concrete capabilities with specific providers. It falls short of anchor 5 because it rests on a single verb with a capability list rather than multiple distinct concrete actions, and refund handling appears only in the 'when' clause, leaving minor gaps.

4 / 5

Completeness

Explicitly 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 concrete trigger phrases, matching the anchor-5 example structure. Third-person voice is used correctly.

5 / 5

Trigger Term Quality

Includes strong natural keywords users would actually say: "Stripe", "PayPal", "Square", "subscriptions", "webhooks", "checkout flows", "recurring billing", "refunds", "disputes". Good coverage but a few natural terms/synonyms are missing (e.g. "accept payments", "payment gateway", "invoices"), so it sits between anchors 4 and 5, closer to 4.

4 / 5

Distinctiveness Conflict Risk

Clear niche (payment gateway integration) with named providers and distinct trigger phrases (checkout, recurring billing, refunds/disputes) that are unlikely to fire for unrelated skills. Minimal conflict risk with any other skill.

5 / 5

Total

18

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

secondsky/claude-skills

Path

plugins/payment-gateway-integration/skills/payment-gateway-integration/SKILL.md

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.