CtrlK
BlogDocsLog inGet started
Tessl Logo

payment-integration

Integrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.

59

Quality

70%

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 ./.claude/skills/payment-integration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

A well-organized, token-efficient overview with excellent progressive disclosure that defers detail to verified reference files. It is weakened by lacking inline executable guidance and explicit validation checkpoints in its workflows.

Suggestions

Add a short inline executable snippet (e.g. a minimal webhook-verification call or checkout-session creation) so the body is actionable before loading references.

Insert explicit validation checkpoints into the implementation workflow, such as verifying webhook signatures and testing in sandbox before promoting to production.

Surface the sandbox/test-mode requirement and idempotency check as explicit steps in the General Workflow rather than only implying them.

DimensionReasoningScore

Conciseness

The body is a lean overview with tables and a reference index; it explains no concepts Claude already knows and every line earns its place, matching the 'lean and efficient' anchor.

3 / 3

Actionability

The body points to reference files and scripts rather than providing concrete executable guidance inline; it describes where to find instructions instead of instructing, which is incomplete relative to the 'fully executable' anchor.

2 / 3

Workflow Clarity

A general flow ('auth -> products -> checkout -> webhooks -> events') and sequenced per-platform steps exist in implementation-workflows.md, but there are no explicit validation/checkpoint steps for risky webhook-verification or checkout operations, which caps workflow clarity at 2.

2 / 3

Progressive Disclosure

The SKILL.md is a clear overview pointing to well-signaled, one-level-deep references organized per platform, all of which are verified real files, matching the 'clear overview with well-signaled one-level-deep references' anchor.

3 / 3

Total

10

/

12

Passed

Description

67%

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 specific, well-scoped description that names concrete actions and platforms, but it lacks an explicit 'Use when...' trigger clause and misses some common natural-language variations like 'billing', which limit completeness and trigger-term quality.

Suggestions

Add a 'Use when ...' clause naming natural triggers, e.g. 'Use when integrating payment gateways, handling webhooks, or managing subscriptions and licensing.'

Include common user phrasings such as 'billing', 'recurring payments', and 'payment processing' to broaden trigger-term coverage.

Clarify the Paddle/Creem 'MoR' abbreviation on first use so the description is self-contained for users unfamiliar with Merchant-of-Record terminology.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Checkout, webhooks, subscriptions, QR codes, multi-provider orders') and names five specific platforms with their roles, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Strong 'what' is present but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Includes relevant natural terms (payments, checkout, webhooks, subscriptions, QR codes) but omits common variations a user might say such as 'billing', 'payment processing', or 'recurring billing', so coverage is incomplete.

2 / 3

Distinctiveness Conflict Risk

The multi-provider payment-integration niche with named platforms (SePay/VietQR, Polar, Stripe, Paddle, Creem.io) is clearly distinguishable and unlikely to trigger for the wrong skill.

3 / 3

Total

10

/

12

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.

Validation14 / 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: 33 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository
mrgoonie/claudekit-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.