payment-integration

Integrate Stripe, PayPal, and payment processors. Handles checkout flows, subscriptions, webhooks, and PCI compliance. Use PROACTIVELY when implementing payments, billing, or subscription features.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/payment-integration/SKILL.md

Quality

Content

36%Scale 1-5

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

This skill covers important payment integration concepts (webhook security, PCI compliance, idempotency) but fails to provide actionable, executable guidance. It reads more like a checklist of principles than a skill that enables Claude to implement payment integrations. The lack of any code examples is a significant weakness for a technical integration skill, and the absence of a clear workflow with validation steps limits its practical utility.

Suggestions

Add concrete, executable code examples for key operations: Stripe checkout session creation, webhook signature verification (e.g., `stripe.webhooks.constructEvent()`), and idempotent handler patterns with database event ID checks.

Define a clear numbered workflow for payment integration (e.g., 1. Set up test credentials → 2. Implement checkout → 3. Add webhook endpoint → 4. Verify signatures → 5. Test with Stripe CLI → 6. Migrate to production) with explicit validation checkpoints at each step.

Remove boilerplate sections ('Use this skill when/Do not use this skill when') and the 'You are a payment integration specialist' persona statement to save tokens for actual implementation guidance.

Either provide the referenced `resources/implementation-playbook.md` bundle file or inline the most critical implementation patterns directly in the skill.

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary framing ('You are a payment integration specialist...') and sections like 'Use this skill when / Do not use this skill when' that are generic boilerplate. The 'Common Failures' section adds value but the sourcing lines are padding. The core content (Critical Requirements) is reasonably efficient but the overall document could be tightened significantly.	3 / 5
Actionability	Despite covering important concepts (webhook security, idempotency, PCI compliance), the skill provides zero executable code examples. For a payment integration skill, there should be concrete code showing webhook signature verification, Stripe checkout session creation, or idempotent handler patterns. The guidance remains at the 'describe what to do' level rather than 'show how to do it' level.	2 / 5
Workflow Clarity	There is no clear multi-step workflow for implementing a payment integration. The 'Approach' section lists principles (security first, idempotency, etc.) but not a sequenced process. For a skill involving destructive/financial operations, there are no validation checkpoints, no feedback loops for testing payment flows, and no step-by-step integration process.	2 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed examples, which is good progressive disclosure in principle. However, no bundle files are provided, so we can't verify this reference exists. The main file itself has reasonable section structure but inlines content (Common Failures, Output list) that could be better organized or split out.	3 / 5
	Total	10 / 20 Passed

Description

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

This is a strong skill description that clearly identifies its domain (payment processing), names specific platforms and capabilities, and includes an explicit 'Use when' clause with natural trigger terms. Minor improvements could include additional trigger synonyms like 'payment gateway', 'recurring billing', or 'refunds' and a few more concrete actions.

Dimension	Reasoning	Score
Specificity	Lists several specific actions: checkout flows, subscriptions, webhooks, PCI compliance, and names concrete platforms (Stripe, PayPal). Minor gaps—could mention invoicing, refunds, or specific API operations.	4 / 5
Completeness	Clearly answers both 'what' (integrate Stripe/PayPal, handle checkout flows, subscriptions, webhooks, PCI compliance) and 'when' (explicitly states 'Use PROACTIVELY when implementing payments, billing, or subscription features').	5 / 5
Trigger Term Quality	Includes strong natural trigger terms like 'Stripe', 'PayPal', 'payments', 'billing', 'subscriptions', 'checkout', and 'webhooks'. Missing some variations like 'payment gateway', 'recurring billing', 'invoicing', or 'charge'.	4 / 5
Distinctiveness Conflict Risk	Highly distinctive with a clear niche around payment processing. The mention of specific platforms (Stripe, PayPal) and domain-specific terms (PCI compliance, webhooks, checkout flows) make it very unlikely to conflict with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/payment-integration/SKILL.md
Commit: fbdfd63

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.