Stripe Apps
fossasia/eventyay
A skill your agent uses when building, modifying, or reviewing a Stripe App — or when the user describes something that implies one (e.g.
A skill your agent uses when wiring an app to Stripe for payments, subscriptions, Checkout, webhooks or the billing portal — adding a paywall or paid plan, charging recurring fees, and debugging why…
$ npx skills add ericrisco/rsc-harness --skill stripe -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ericrisco/rsc-harness stripe --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/stripe .claude/skills/stripe && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "stripe" agent skill from https://github.com/ericrisco/rsc-harness/tree/main/skills/stripe into .claude/skills/stripe/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stripe", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ericrisco/rsc-harness/tree/main/skills/stripeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ericrisco/rsc-harness --skill stripe -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ericrisco/rsc-harness stripe --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/stripe .agents/skills/stripe && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "stripe" agent skill from https://github.com/ericrisco/rsc-harness/tree/main/skills/stripe into .agents/skills/stripe/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stripe", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ericrisco/rsc-harness --skill stripe -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ericrisco/rsc-harness stripe --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/stripe .cursor/skills/stripe && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "stripe" agent skill from https://github.com/ericrisco/rsc-harness/tree/main/skills/stripe into .cursor/skills/stripe/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stripe", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ericrisco/rsc-harness.git --path skills/stripe--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ericrisco/rsc-harness --skill stripe -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ericrisco/rsc-harness stripe --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/stripe .gemini/skills/stripe && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "stripe" agent skill from https://github.com/ericrisco/rsc-harness/tree/main/skills/stripe into .gemini/skills/stripe/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stripe", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ericrisco/rsc-harness stripeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ericrisco/rsc-harness --skill stripe -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/stripe .github/skills/stripe && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "stripe" agent skill from https://github.com/ericrisco/rsc-harness/tree/main/skills/stripe into .github/skills/stripe/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stripe", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ericrisco/rsc-harness --skill stripe -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ericrisco/rsc-harness stripe --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/stripe .opencode/skills/stripe && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "stripe" agent skill from https://github.com/ericrisco/rsc-harness/tree/main/skills/stripe into .opencode/skills/stripe/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stripe", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
stripeA skill your agent uses when wiring an app to Stripe for payments, subscriptions, Checkout, webhooks or the billing portal — adding a paywall or paid plan, charging recurring fees, and debugging why…
Stripe is an agent skill from ericrisco/rsc-harness. Use when wiring an app to Stripe for payments, subscriptions, Checkout, webhooks or the billing portal — adding a paywall or paid plan, charging recurring fees, and debugging why a completion event never fires, why signature verification fails, or why a webhook fires twice and duplicates the order. NOT a generic non-Stripe inbound event receiver (that is webhooks), NOT the invoice document's legal form (that is invoicing), NOT deciding what to charge (that is pricing).
Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and reference files (for example `evals/README.md`, `evals/cases.yaml` and `references/going-live.md`).
It sits in Backend & APIs, covering Webhooks. It works with Stripe. The repository describes itself as: Your agent invents things because it has no memory, and can't touch your database because it has no arms. rsc is the meta-harness that gives it both, plus the trade to know the… The licence is MIT.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit e3d5b33. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
stripeFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
STRIPE_SECRET_KEYSTRIPE_WEBHOOK_SECRETFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Stripe loads about 2.9k tokens when it runs, and up to ~4.5k if it reads all its reference files. Until then it costs about 122 tokens; SKILL.md has 881 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from ericrisco/rsc-harness at commit e3d5b33, republished under its MIT licence (© ericrisco). 881 words, ~2,935 tokens.
.claude/skills/stripe/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.Wire an app to Stripe for one-time payments and subscriptions: a Checkout
Session to take money, a signature-verified webhook to learn the outcome, and
the billing portal so customers manage themselves. Targets stripe-node v22.x
(API version 2026-05-27.dahlia).
The one rule everything else hangs off:
Use when: adding Checkout or a paywall; taking a one-time or recurring
charge; receiving Stripe webhooks; letting users cancel/upgrade via the portal;
debugging No signatures found matching, double-fired events, or a
checkout.session.completed that never arrives.
Do NOT use for:
webhooks. This skill only covers
Stripe's Stripe-Signature scheme and event model.api-connector-builder.| You need | Use | Why |
|---|---|---|
| A link to sell one product, zero code | Payment Link | No backend; Stripe hosts everything. Outgrow it fast. |
| Hosted checkout, full control of session | Checkout Session | The default. Stripe hosts the page, handles SCA/3DS, PCI scope is minimal. |
| Your own embedded payment form | Payment Element + Checkout Session | Custom UI, but you render the form. Use the Element with a Checkout Session, not raw PaymentIntents, unless you have a reason. |
Default to Checkout Session unless a requirement forces otherwise.
Customer ──> Price (you defined it in Stripe) ──> Checkout Session
│ │
│ customer pays (hosted)
▼ ▼
your DB <── webhook (verified) ── Event <── Subscription / Invoice
(a cache) (the real state, in Stripe)Env vars used throughout — read from the environment, never hard-code:
STRIPE_SECRET_KEY — sk_test_… in dev, sk_live_… in prod.STRIPE_WEBHOOK_SECRET — whsec_…, one per endpoint; differs in test vs live.import Stripe from "stripe";
// Pin apiVersion explicitly so a dashboard-level version bump can never change
// your API behavior under you. Match the version your SDK release ships with.
export const stripe = new Stripe(process.env.STRIPE_SECRET_KEY!, {
apiVersion: "2026-05-27.dahlia",
});// Subscription mode — recurring price.
const session = await stripe.checkout.sessions.create({
mode: "subscription",
line_items: [{ price: "price_123", quantity: 1 }], // a recurring Price ID
success_url: `${BASE}/success?session_id={CHECKOUT_SESSION_ID}`,
cancel_url: `${BASE}/pricing`,
// Tie the session to YOUR user so the webhook can find the right row.
client_reference_id: userId,
// 14-day trial; omit for immediate billing.
subscription_data: { trial_period_days: 14 },
});
// Redirect the browser to session.url.// Payment mode — one-time charge (e.g. a digital download).
const session = await stripe.checkout.sessions.create({
mode: "payment",
line_items: [{ price: "price_onetime", quantity: 1 }],
success_url: `${BASE}/success?session_id={CHECKOUT_SESSION_ID}`,
cancel_url: `${BASE}/`,
client_reference_id: userId,
});success_url is a UX redirect, not proof of payment. The customer can close the
tab before it loads, or hit the URL directly. Grant access from the webhook,
not the redirect.
This is where integrations break. Three non-negotiables:
constructEvent recomputes the signature
over the exact bytes Stripe sent. Any middleware that parses/re-serializes
the body (e.g. express.json() on this route) changes those bytes and you
get No signatures found matching the expected signature.event.id, persisting the idempotency record in the same
transaction as the business write. Default replay tolerance is 5 minutes.// Express. The route gets the RAW body; do NOT mount express.json() here.
app.post("/webhook", express.raw({ type: "application/json" }), async (req, res) => {
let event: Stripe.Event;
try {
event = stripe.webhooks.constructEvent(
req.body, // raw Buffer, untouched
req.headers["stripe-signature"]!, // header name is lowercase
process.env.STRIPE_WEBHOOK_SECRET!,
);
} catch (err) {
return res.status(400).send(`Webhook Error: ${(err as Error).message}`);
}
// Dedupe + record in one transaction; skip if we have seen this event.id.
const fresh = await recordEventOnce(event.id, event.type);
if (!fresh) return res.status(200).send(); // already processed; ack and stop
// Return 2xx FAST. Hand heavy work to a queue/background job if it is slow.
switch (event.type) {
case "checkout.session.completed": {
const s = event.data.object as Stripe.Checkout.Session;
await grantAccess(s.client_reference_id!, s.customer as string);
break;
}
case "customer.subscription.updated":
case "customer.subscription.deleted": {
const sub = event.data.object as Stripe.Subscription;
await syncSubscription(sub.customer as string, sub.status); // mirror state
break;
}
case "invoice.payment_failed":
// dunning lives here; see references/webhook-events.md
break;
}
res.status(200).send();
});See references/webhook-events.md for the full
event catalog per flow (subscription lifecycle, one-time payment, dunning) and
what each event should do to your DB.
// Next.js App Router — read the raw text yourself; do not use req.json().
// app/api/webhook/route.ts
export async function POST(req: Request) {
const body = await req.text(); // raw string
const sig = req.headers.get("stripe-signature")!;
const event = stripe.webhooks.constructEvent(body, sig, secret);
// ...handle, then:
return new Response(null, { status: 200 });
}// Edge / Cloudflare Workers — synchronous crypto is unavailable. Use the async
// API with the Web Crypto provider.
const event = await stripe.webhooks.constructEventAsync(
body, sig, secret, undefined, Stripe.createSubtleCryptoProvider(),
);For a subscription paywall, listen to exactly these — listening to "all events" is discouraged and buries you in noise:
checkout.session.completed, customer.subscription.created,
customer.subscription.updated, customer.subscription.deleted,
invoice.paid, invoice.payment_failed.
Do not build cancel/upgrade/update-card UI. Stripe hosts it.
const portal = await stripe.billingPortal.sessions.create({
customer: stripeCustomerId, // the Customer you stored
return_url: `${BASE}/account`,
});
// Redirect to portal.url — it is short-lived; mint it on demand, never cache it.A retried POST (network blip, double-click) can create two subscriptions. Pass an idempotency key derived from the operation, not a random one:
await stripe.checkout.sessions.create(params, {
idempotencyKey: `checkout:${userId}:${planId}`,
});stripe login
stripe listen --forward-to localhost:3000/api/webhook # prints a whsec_… secret
stripe trigger checkout.session.completed # fire a real test eventPut the printed whsec_… in STRIPE_WEBHOOK_SECRET for local runs. Hand-built
JSON will never pass signature verification — that is the point.
Compact checklist; depth in references/going-live.md:
apiVersion pinned explicitly in the client.sk_test_/whsec_ (test) for live values via env, not code.| Bad | Good | Why |
|---|---|---|
express.json() on the webhook route | express.raw() / req.text() | Re-serialized body breaks the signature → No signatures found matching. |
No constructEvent — trust the payload | Always verify the signature | Anyone can POST fake events to an unverified endpoint. |
Grant access on the success_url redirect | Grant on checkout.session.completed | The redirect is UX, not proof; it can be skipped or forged. |
| DB writes, then return 200 | Return 200 fast, queue slow work | Timeouts make Stripe retry → duplicate delivery. |
| Process every delivery | Dedupe on event.id in the write txn | Events are unordered and at-least-once. |
Hard-coded sk_live_… in source | process.env.STRIPE_SECRET_KEY | Leaked keys = drained account; never commit them. |
No apiVersion | Pin it explicitly | A dashboard version bump silently changes your API behavior. |
| Poll the API for subscription state | React to webhooks | Polling is slow, rate-limited, and races real events. |
| Listen to all event types | Subscribe to the allowlist | Noise, wasted handling, accidental side effects. |
| Cache the portal/session URL | Mint per request | These URLs are short-lived and single-use. |
webhooks — generic, non-Stripe inbound event receivers.© ericrisco, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 5 other files (scripts, references) in skills/stripe of ericrisco/rsc-harness.
Open the folder on GitHubat commit e3d5b33
Stripe next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Stripe this skillericrisco/rsc-harness | 167 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Stripe Appsfossasia/eventyay | 1.7k | 2 repos | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| Stripe Best Practiceskanchengw/cnllm | 175 | 3 repos | ~925 | Automated safety check: Pass | Apache-2.0 | |
| Cashier Stripe Developmentluadotsh/lua | 343 | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Stripe Best Practicesfossasia/eventyay | 1.7k | 1 repos | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Stripe Integrationwshobson/agents | 40k | 10 repos | ~1k | Automated safety check: Pass | MIT |
fossasia/eventyay
A skill your agent uses when building, modifying, or reviewing a Stripe App — or when the user describes something that implies one (e.g.
kanchengw/cnllm
Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial…
luadotsh/lua
Handles Laravel Cashier Stripe integration including subscriptions, webhooks, Stripe Checkout, invoices, charges, refunds, trials, coupons, metered billing, and payment failure handling.
fossasia/eventyay
Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents)…
wshobson/agents
Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks.
waynesutton/builder-skills
Adds HTTP endpoints in convex/http.ts: webhook receivers with signature checks, REST style routes, CORS, auth headers, streaming responses, and file uploads over HTTP.
ericrisco/rsc-harness
A skill your agent uses when designing or analyzing a controlled experiment — falsifiable hypothesis, sample size from an MDE, reading significance/CI/power, CUPED, or rescuing tests that won't go…
ericrisco/rsc-harness
A skill your agent uses when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast…
ericrisco/rsc-harness
A skill your agent uses when running or fixing paid acquisition on Google or Meta — campaign structure (Performance Max, Demand Gen, Search, Advantage+), platform-fit creative, budget/scaling rules…
ericrisco/rsc-harness
A skill your agent uses when measuring whether an LLM or agent system actually got better and gating merges on it: golden sets, fixing an inflated LLM-as-judge, scoring RAG (faithfulness, contextual…
ericrisco/rsc-harness
A skill your agent uses when a creative goal must become a finished media file: pick and order generative-media models per modality — AI voiceover, image-to-video clips, score — then glue them with…
ericrisco/rsc-harness
A skill your agent uses when instrumenting product or web analytics — GA4/PostHog SDK wiring, event taxonomy, funnels, double-counted events, consent gating, PII scrubbing.
Works with
Categories
A skill your agent uses when wiring an app to Stripe for payments, subscriptions, Checkout, webhooks or the billing portal — adding a paywall or paid plan, charging recurring fees, and debugging why…. Stripe is an agent skill from ericrisco/rsc-harness. Use when wiring an app to Stripe for payments, subscriptions, Checkout, webhooks or the billing portal — adding a paywall or paid plan, charging recurring fees, and debugging why a completion event never fires, why signature verification fails, or why a webhook fires twice and duplicates the order.
Stripe fits situations like: wiring an app to Stripe for payments; the billing portal — adding a paywall; charging recurring fees; debugging why a completion event never fires.
Run `npx skills add ericrisco/rsc-harness --skill stripe -a claude-code`. Or copy the skill folder (skills/stripe in ericrisco/rsc-harness) into .claude/skills/stripe in your project. Claude Code loads it when a task matches its description.
Run `npx skills add ericrisco/rsc-harness --skill stripe -a codex`. Or copy the skill folder (skills/stripe in ericrisco/rsc-harness) into .agents/skills/stripe in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ericrisco/rsc-harness --skill stripe -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/stripe, .gemini/skills/stripe, .github/skills/stripe and .opencode/skills/stripe in your project.
Going by SKILL.md and its folder, Stripe needs a shell for the scripts in its folder, the command-line tools its instructions call (stripe) and credentials named STRIPE_SECRET_KEY and STRIPE_WEBHOOK_SECRET. Our summary lists: Node.js; A Bash shell; A credential in STRIPE_SECRET_KEY; A credential in STRIPE_WEBHOOK_SECRET.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Stripe is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Stripe: Stripe Apps (fossasia/eventyay, 1.7k stars), Stripe Best Practices (kanchengw/cnllm, 175 stars), Cashier Stripe Development (luadotsh/lua, 343 stars) and Stripe Best Practices (fossasia/eventyay, 1.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
ericrisco (a GitHub user) maintains it in ericrisco/rsc-harness, which has 167 GitHub stars. The repository holds 227 skills in this directory. The repository was last updated on October 7, 2026.
Source: ericrisco/rsc-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.