CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

payment-integration

Payment gateway integration. Providers: SePay (Vietnamese: VietQR, bank transfer, cards), Polar (global SaaS: subscriptions, usage-based billing). SDKs: Node.js, PHP, Python, Go, Laravel, Next.js. Capabilities: checkout flows, subscription management, webhooks, QR code generation, benefit automation, tax compliance. Actions: integrate, implement, configure, handle payments/subscriptions/webhooks. Keywords: payment gateway, SePay, Polar, VietQR, bank transfer, subscription, usage-based billing, checkout, webhook, QR code, API key, OAuth2, product management, customer portal, tax compliance, MoR, recurring payment, invoice. Use when: integrating payment processing, implementing checkout, managing subscriptions, handling payment webhooks, generating payment QR codes, building billing systems.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

63%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 a well-structured progressive-disclosure hub with verified reference files and clear, sequenced per-platform workflows. Its weaknesses are a padded 'Key Capabilities'/'Instructions' tail that duplicates earlier sections and generic advice, and missing executable details such as script invocation syntax or minimal quick-start code for either platform.

Suggestions

Trim the 'Key Capabilities' section (it duplicates the description, 'When to Use', and 'Platform Selection' lists) and cut generic Instructions steps like 'Test thoroughly in sandbox' and 'Monitor and optimize' to raise conciseness toward the token-efficient anchors.

Add a minimal quick-start snippet per platform (e.g., SDK install plus client initialization) and show invocation syntax for the bundled scripts (e.g., 'node scripts/polar-webhook-verify.js <payload> <signature>') so guidance is copy-paste executable.

Replace vague Instructions steps like 'Implement authentication using platform-specific methods' with pointers to the exact reference file and section that contains the concrete auth steps.

DimensionReasoningScore

Conciseness

The Quick Reference and Implementation Workflow sections are lean and functional, but roughly a quarter of the body is trimmable: the 'Key Capabilities' section repeats items already stated in 'When to Use' and 'Platform Selection' (e.g., 'Usage-based billing', 'Automated benefits (GitHub, Discord, licenses)' each appear multiple times), and the 'Instructions' section offers generic filler like 'Test thoroughly in sandbox before production' and 'Monitor and optimize using platform analytics' that Claude already knows. This is more than the 'minor instances' of anchor 4 but far from the padded explanations of anchor 2.

3 / 5

Actionability

As an instruction-only routing skill the concrete file-load directives ('Load references/sepay/overview.md for auth setup', 'Use scripts/sepay-webhook-verify.js for webhook verification') are specific, but key execution details are missing: no script invocation syntax (e.g., a command line showing how to run the verify scripts), no quick-start snippet for either platform, and the 'Instructions' section is high-level direction ('Implement authentication using platform-specific methods') rather than executable guidance. This lands on anchor 3 ('some concrete guidance but incomplete; missing key details'), not 2 since the navigation directives are exact and directly followable.

3 / 5

Workflow Clarity

Both per-platform sequences are clearly ordered with embedded checkpoints (webhook verification scripts at a specific step, sandbox testing, and best-practices review for production readiness), matching anchor 4's 'clear sequence with most checkpoints present'. It is not anchor 5 because there are no explicit feedback loops (verify, and if verification fails, what to fix and re-check) or error-recovery guidance; it is above anchor 3 because checkpoints are explicit, not merely implied.

4 / 5

Progressive Disclosure

The body is a model overview: every one of the 14 reference files and 3 scripts named in Quick Reference and the Implementation Workflow exists in the bundle (verified against references/sepay/, references/polar/, and scripts/), references are exactly one level deep, each is signaled with a one-line description, and load order is specified per workflow. This matches anchor 5 ('clear overview with well-signaled one-level-deep references; easy navigation'); the unlisted support files (test-scripts.js, .env.example) are a non-issue.

5 / 5

Total

15

/

20

Passed

Description

91%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 that explicitly states what the skill does and when to use it, with comprehensive natural trigger terms and a clearly defined two-provider niche. Its only weaknesses are generic action verbs and a few broad keywords that modestly widen conflict risk.

DimensionReasoningScore

Specificity

The description lists several specific capability areas ('checkout flows, subscription management, webhooks, QR code generation, benefit automation, tax compliance') anchored to two named providers, but the action verbs themselves ('integrate, implement, configure, handle') are generic templates rather than fully concrete actions, so it falls just short of the comprehensive anchor 5. It is well above anchor 3, which covers only 1-2 concrete actions.

4 / 5

Completeness

It explicitly answers 'what' ('Payment gateway integration. Providers: SePay... Capabilities: checkout flows, subscription management, webhooks...') and 'when' via a literal 'Use when:' clause with concrete trigger phrases ('integrating payment processing, implementing checkout, managing subscriptions, handling payment webhooks'). This matches the anchor 5 example structure exactly; the 'Use when' clause is present so the completeness cap of 3 does not apply.

5 / 5

Trigger Term Quality

The keyword list provides comprehensive natural-term coverage including synonyms users would actually say: 'payment gateway, SePay, Polar, VietQR, bank transfer, subscription, recurring payment, invoice, checkout, webhook, QR code'. The domain has no meaningful file extensions, so the synonym coverage ('subscription'/'recurring payment', 'bank transfer'/'VietQR') satisfies the anchor 5 standard; it is not score 4 since no common variations are obviously missing.

5 / 5

Distinctiveness Conflict Risk

Naming SePay and Polar creates a clear niche with distinct triggers, but broad terms like 'subscription', 'webhook', 'invoice', and 'API key' create minor overlap risk with closely related billing, invoicing, or generic webhook skills. It sits between anchor 4 ('minor overlap risk with closely related skills') and anchor 5, settling on 4 because the generic keyword tail slightly widens the trigger surface beyond the payment-gateway niche.

4 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 25 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

samhvw8/dot-claude

Path

skills/payment-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.