CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

payment-integration

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

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

53%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's substantive middle (security requirements, common failures, deliverables) is solid and domain-specific, but it is bookended by generic boilerplate sections and lacks any executable code despite promising code outputs. Tightening the padding and adding one concrete webhook/checkout code pattern with an explicit test-mode-to-production validation gate would lift it substantially.

Suggestions

Delete the boilerplate 'Use this skill when', 'Do not use this skill when', 'Instructions', and role-play sections — they are either tautological or duplicate the frontmatter description and add no payment-specific value.

Add at least one executable example (e.g., a Stripe webhook handler showing raw-body signature verification and the sub-200ms 2xx return) since the Output section promises code and endpoint implementations.

Turn the 'Approach' principles into a sequenced workflow with an explicit validation gate, e.g., 'build in test mode → verify with test cards and delivered webhook events → only then switch API keys to production', to give payments the feedback loop they require.

DimensionReasoningScore

Conciseness

The core sections (Critical Requirements, Approach, Output) are dense and payment-specific, but roughly the first 15 lines are padding: the tautological 'Do not use this skill when' bullets ('The task is unrelated to payment integration'), the generic 'Instructions' bullets ('Clarify goals, constraints, and required inputs'), the role-play line, and a 'Use this skill when' section that duplicates the frontmatter. That is more than minor trimmable over-explanation (4) but the bulk is still efficient, so it sits at 3 rather than 2.

3 / 5

Actionability

The Critical Requirements section gives genuinely concrete rules ('verify webhook signatures using official SDK libraries', 'Return 2xx status within 200ms', 'Store event IDs in your database'), but there is no executable code, no SDK method names, no endpoint or schema examples — yet the Output section promises 'Payment integration code', 'Webhook endpoint implementations', and 'Database schema'. This is concrete-but-incomplete guidance, matching anchor 3 rather than the mostly-executable anchor 4.

3 / 5

Workflow Clarity

The 'Approach' list reads as prioritized principles rather than an execution sequence, and validation checkpoints are implicit at best ('Test mode first, with clear migration path to production' is the only one). For operations as risky as charging money and processing webhooks, there is no explicit validate-then-proceed or test-then-migrate loop, which fits anchor 3 (sequence present, checkpoints missing or implicit) and rules out 4.

3 / 5

Progressive Disclosure

No bundle files exist and the ~68-line body is organized into clearly headed sections with all content at one level and no buried references, which is good structure with content appropriately placed for this size. It falls short of 5 because the body exceeds the under-50-line simple-skill case and detail-heavy material (Common Failures, webhook/PCI deep-dives) could live in reference files for a multi-faceted domain.

4 / 5

Total

13

/

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 that clearly states what the skill does and when to use it, with named providers and natural trigger terms. Only minor improvements possible: drop the generic 'and payment processors' tail and add a few more synonyms (e.g., invoices, payment gateway).

DimensionReasoningScore

Specificity

Names concrete providers ('Integrate Stripe, PayPal') and lists several specific capability areas ('checkout flows, subscriptions, webhooks, and PCI compliance'). The trailing 'and payment processors' is generic and coverage omits items like refunds/disputes and error handling that the body covers, so it falls just short of the comprehensive anchor at 5.

4 / 5

Completeness

Explicitly answers both questions: what ('Integrate Stripe, PayPal, and payment processors. Handles checkout flows, subscriptions, webhooks, and PCI compliance') and when ('Use when implementing payments, billing, or subscription features') with concrete trigger phrases, matching the top anchor's structure.

5 / 5

Trigger Term Quality

Includes natural terms users would say — 'Stripe', 'PayPal', 'payments', 'billing', 'subscription', 'checkout' — in an explicit trigger clause ('Use when implementing payments, billing, or subscription features'). A few natural variations are missing (e.g., 'invoice', 'payment gateway', 'Square'), which keeps it below the comprehensive-synonym anchor at 5 and clearly above the sparse coverage at 3.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (payment/checkout integration) with distinct triggers — named providers (Stripe, PayPal), webhooks, PCI compliance, subscriptions — making it unlikely to fire for unrelated skills; the generic 'payment processors' tail adds only minimal overlap risk.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

rmyndharis/antigravity-skills

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.