CtrlK
BlogDocsLog inGet started
Tessl Logo

stripe-integration

Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks. Use when integrating Stripe payments, building subscription systems, or implementing secure checkout flows.

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugins/payment-processing/skills/stripe-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.

A well-organized, largely executable reference that appropriately offloads detail to one verified deep reference. Its main weakness is workflow clarity: payment and webhook handling are presented conceptually without validation/verification checkpoints, which caps that dimension at 3.

Suggestions

Add an explicit multi-step webhook workflow with validation checkpoints: verify the signature, guard against replay/idempotency, then process — so workflow_clarity can exceed the destructive-operations cap of 3.

Trim the Core Concepts glosses (Product/Price/Subscription/Invoice) or move them into references/details.md to lift conciseness toward anchor 5.

Include a minimal inline webhook-handler code example (event loop + signature check) alongside the critical-events list to close the actionability gap.

DimensionReasoningScore

Conciseness

The body is mostly lean with bullets and executable snippets, but the Core Concepts glosses (Product/Price/Subscription/Invoice) lightly over-explain Stripe model basics Claude largely knows, keeping it just below anchor 5.

4 / 5

Actionability

Quick Start and Testing provide copy-paste-ready Python and concrete test card numbers, while named webhook events are actionable; the main gap is that webhook-handler implementation is not shown inline, so it is not fully anchor-5.

4 / 5

Workflow Clarity

The body reads as conceptual reference material rather than a sequenced workflow, and payment plus webhook handling — sensitive operations — lack validation checkpoints (signature verification, idempotency), so workflow_clarity is capped at 3 per the destructive/batch guidance.

3 / 5

Progressive Disclosure

Clear section structure with a single well-signaled, one-level-deep reference to references/details.md (verified to exist); the Core Concepts block is slightly detailed for an overview, leaving a minor organization gap versus anchor 5.

4 / 5

Total

15

/

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, third-person description that clearly answers both what the skill does and when to use it, anchored on Stripe-specific triggers. Minor specificity gaps (no refunds/disputes) keep specificity and trigger_term_quality at 4 rather than 5.

DimensionReasoningScore

Specificity

Lists several concrete capabilities (checkout, subscriptions, webhooks, PCI-compliant flows) but omits refunds, disputes, and payment-method management that appear in the body, leaving minor coverage gaps rather than full anchor-5 comprehensiveness.

4 / 5

Completeness

Explicitly states the what ('Implement Stripe payment processing for ... checkout, subscriptions, and webhooks') and the when ('Use when integrating Stripe payments, building subscription systems, or implementing secure checkout flows'), matching the anchor-5 pattern.

5 / 5

Trigger Term Quality

Natural phrases users would say are present ('integrating Stripe payments', 'subscription systems', 'checkout flows'), but synonyms like 'billing' or payment-method terms are missing, so it is not a full anchor-5.

4 / 5

Distinctiveness Conflict Risk

Brand-named Stripe-specific triggers carve a clear niche with minimal overlap risk against other skills.

5 / 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
wshobson/agents
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.