CtrlK
BlogDocsLog inGet started
Tessl Logo

stripe-integration

Master Stripe payment processing integration for robust, PCI-compliant payment flows including checkout, subscriptions, webhooks, and refunds.

58

Quality

68%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/stripe-integration/SKILL.md

The canonical home for this skill is stripe-integration in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

61%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 body is highly actionable with executable code, but it is verbose for a SKILL.md, lacks validation feedback loops for irreversible payment operations, and references bundle files that are missing.

Suggestions

Move the pattern catalog into the referenced bundle files (references/*.md, assets/*.py) and actually ship them, so SKILL.md becomes a lean overview with one-level-deep pointers.

Add explicit validation/reconciliation steps (e.g., verify PaymentIntent status, confirm webhook signature before fulfilling, reconcile invoice paid state) for destructive/batch payment operations.

Fix the broken 'resources/implementation-playbook.md' reference to match the 'references/' directory, and trim the Core Concepts section that restates Stripe basics.

DimensionReasoningScore

Conciseness

Mostly efficient code-centric content, but the ~450-line body re-explains Stripe basics Claude already knows (e.g., 'Product: What you're selling', 'Price: How much and how often') and duplicates webhook-handling across the secure-endpoint and best-practices sections.

3 / 5

Actionability

Copy-paste-ready, executable Python/JS covering the common cases — checkout sessions, payment intents, subscriptions, customer portal, webhook verification, refunds, disputes, and test cards.

5 / 5

Workflow Clarity

Sequences appear in places (e.g., the test flow), but there are no explicit validation checkpoints or validate->fix->retry feedback loops for destructive financial operations (charges, refunds), which caps workflow clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

A large amount of content that belongs in separate files is inlined, and the Resources section points to files (references/*.md, assets/*.py, resources/implementation-playbook.md) that do not exist on disk; the 'resources/' path also mismatches the listed 'references/' directory.

2 / 5

Total

13

/

20

Passed

Description

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

The description is specific, distinctive, and rich in natural trigger terms, but it omits any explicit 'when to use' guidance, which the rubric caps at completeness 3.

Suggestions

Append an explicit 'Use when ...' trigger clause (e.g., 'Use when integrating Stripe payments, building checkout or subscription flows, or handling webhooks and refunds') to raise completeness.

Add a couple of common synonyms ('billing', 'invoices', 'charges') to broaden natural trigger coverage.

Keep the third-person voice and concise phrasing already present — do not pad with marketing language.

DimensionReasoningScore

Specificity

Names the Stripe domain and lists multiple concrete actions — 'checkout, subscriptions, webhooks, and refunds' — giving comprehensive coverage of the payment integration surface.

5 / 5

Completeness

Clearly answers 'what' the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Strong natural terms users say ('Stripe', 'payment processing', 'checkout', 'subscriptions', 'webhooks', 'refunds', 'PCI-compliant'), but a few common variations ('billing', 'invoices', 'charges') are absent.

4 / 5

Distinctiveness Conflict Risk

Clearly Stripe-specific niche with distinct triggers ('Stripe payment processing', PCI-compliant flows); minimal risk of triggering for an unrelated skill.

5 / 5

Total

17

/

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.

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: 8 missing

Warning

Total

14

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.