CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

66

Quality

78%

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

68%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 skill is actionable and well-structured with a clean one-level reference for PayPal, but it reads as a code catalog rather than a guided workflow and lacks validation checkpoints for destructive refund operations. Consolidating the redundant checklist/best-practices sections would improve conciseness.

Suggestions

Add a sequenced integration workflow with explicit validation checkpoints (e.g. verify webhook signature, test refund in sandbox, confirm capture status) before destructive refund/capture operations.

Merge the Security Checklist and Best Practices Do/Don't lists into a single deduplicated section to remove redundancy.

Provide a Square implementation or reference file, or drop Square from the description to avoid an unfulfilled capability claim.

DimensionReasoningScore

Conciseness

The body is mostly executable code with minimal prose and assumes Claude's competence, but the Security Checklist and Best Practices Do/Don't lists overlap (both cover webhook verification, sandbox testing, official SDKs), adding minor redundancy.

4 / 5

Actionability

Provides copy-paste-ready PaymentService and webhook code plus a full PayPal reference file, but minor gaps remain: the webhook snippet references undefined handlePaymentSuccess/handlePaymentFailed and an undefined app, and Square (named in the description) has no implementation.

4 / 5

Workflow Clarity

Content is organized as topical code sections rather than a sequenced workflow, and destructive operations like refunds lack explicit validation checkpoints or feedback loops; the destructive-operation cap prevents scoring above 3.

3 / 5

Progressive Disclosure

Good one-level-deep structure: SKILL.md keeps Stripe inline and clearly signals references/paypal-integration.md with a bulleted content preview, though Square is mentioned with no corresponding reference and the main file could split Stripe detail further.

4 / 5

Total

15

/

20

Passed

Description

88%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.

The description is strong: it states concrete capabilities, names specific providers, and gives explicit 'Use when' triggers covering checkout, recurring billing, and refunds/disputes. Minor room to tighten trigger-term synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Integrates payment processing', 'subscriptions, webhooks, and PCI compliance' across three named providers — giving comprehensive coverage rather than a single generic action.

5 / 5

Completeness

Explicitly answers both 'what' ('Integrates payment processing ... including subscriptions, webhooks, and PCI compliance') and 'when' ('Use when implementing checkout flows, recurring billing, or handling refunds and disputes') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases like 'checkout flows', 'recurring billing', 'refunds and disputes' are present and user-facing, but a few common synonyms (e.g. 'subscription billing', 'payment processing') are not enumerated.

4 / 5

Distinctiveness Conflict Risk

Named providers (Stripe, PayPal, Square) and specific triggers carve a clear niche with minimal conflict, though breadth across three gateways leaves minor overlap with general e-commerce/billing skills.

4 / 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
secondsky/claude-skills
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.