stripe-payments

Stripe payment integration patterns, Checkout Sessions, billing/subscriptions, Connect platforms, and API best practices. Use when building, modifying, or reviewing any Stripe integration — including accepting payments, building marketplaces, setting up subscriptions, or implementing secure key handling.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

93%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 an exceptionally lean, actionable Stripe reference: concrete commands and API calls, explicit API-selection routing, and well-organized sections with no padding. The only soft spot is workflow_clarity, where validation is implied rather than presented as an explicit feedback loop.

Suggestions

Add an explicit validate→fix→retry sequence for webhook signature verification (e.g., numbered steps: capture raw body → verify → on failure, log signature header and retry) to lift workflow_clarity to 5.

Consider a short 'Verify before promoting' checklist for new API versions (probe with Stripe-Version header, run test triggers, confirm no removed-field errors) to make the version-upgrade workflow an explicit checkpoint loop.

Dimension	Reasoning	Score
Conciseness	The body is a dense, lean reference with no concept explanations — every bullet ('Restricted keys (rk_) over secret keys (sk_)', 'Store Stripe object IDs in columns accommodating 255 chars') earns its place; time-sensitive breaking-change notes are framed as old-patterns guidance and the version pin is essential one-line operational data.	5 / 5
Actionability	Provides copy-paste-ready commands ('stripe listen --forward-to localhost:3000/api/webhooks', 'stripe trigger <event> --api-version 2026-03-25.dahlia', 'stripe plugin install projects') and exact API calls ('POST /v2/core/accounts', 'stripe.charges.retrieve(pi.latest_charge)'), covering common cases concretely.	5 / 5
Workflow Clarity	The API-selection section gives an explicit preference order (Payment Links → Checkout → Payment Element) and routing rules, and validation checkpoints appear (verify webhook signatures against the raw body; probe a new version via the Stripe-Version header before promoting), but no explicit validate→fix→retry loop is spelled out. Not 5 because checkpoints are implied rather than presented as a sequenced feedback loop; not 3 because concrete sequencing and validation cues are present.	4 / 5
Progressive Disclosure	Under 50 lines with no bundle files (references/scripts/assets absent), organized into clear sections (Never use, API selection, Gotchas) with external doc links grouped at the bottom — the simple-skill exception applies and the structure is easy to navigate.	5 / 5
	Total	19 / 20 Passed

Description

100%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 exemplary: it states concrete capabilities, provides natural trigger terms users would say, and explicitly pairs a 'what' with a 'when' clause. It is clearly niched to Stripe integrations with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'Checkout Sessions, billing/subscriptions, Connect platforms, and API best practices' plus 'secure key handling' — matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.	5 / 5
Completeness	Explicitly answers both what ('Stripe payment integration patterns, Checkout Sessions, billing/subscriptions, Connect platforms') and when ('Use when building, modifying, or reviewing any Stripe integration — including accepting payments, building marketplaces, setting up subscriptions'), matching the score-5 anchor with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural user-facing phrases are present — 'Stripe integration', 'accepting payments', 'building marketplaces', 'setting up subscriptions' — covering the terms a user would actually say, fitting the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	Scoped to a clear Stripe-payments niche with distinct triggers and minimal overlap risk with other skills, matching the clear-niche anchor.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: monkilabs/opencastle
Path: src/orchestrator/plugins/stripe/SKILL.md
Commit: c0f4566

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.