Stripe
PaymentsCommonly used with
Skills using Stripe (70)
onecli-gateway
OneCLI Gateway: transparent HTTPS proxy that injects stored credentials into outbound calls. You MUST use this skill when the user asks you to read emails, check calendar, access GitHub repos, create issues, check Stripe payments, or interact with ANY external service or API. Do NOT use browser extensions or OAuth CLI tools. Make HTTP requests directly; the gateway injects credentials automatically.
ops-integrate
OPS on-demand: This skill should be used when the user asks to "add an API", "integrate SaaS", or…
stripe-best-practices
Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial accounts, integration surfaces (Checkout, Payment Element), migrating from deprecated Stripe APIs, and security best practices (API key management, restricted keys, webhooks, OAuth). Use when building, modifying, or reviewing any Stripe integration — including accepting payments, building marketplaces, integrating Stripe, processing payments, setting up subscriptions, creating connected accounts, or implementing secure key handling.
stripe-projects
Use when setting up a new app or local repo with Stripe Projects, provisioning a software stack, or bootstrapping the Projects CLI from a coding agent.
geo-audit
Runs a one-command technical GEO audit on any domain. Checks AI crawler access, llms.txt presence, server-side rendering, sitemap, and schema markup. Streams results live and ends with a 0–100 score plus the top 3 prioritized fixes. Built to be both genuinely useful and great to demo on camera.
google-ad-scraper
Scrape competitor ads from Google Ads by domain. Returns ad creatives, formats, and campaign details. Use for competitive ad research and messaging analysis.
git-workflow
Git 工作流专家。规范化版本控制，确保提交历史清晰可追溯。支持 Conventional Commits 规范、Pull Request 最佳实践、分支管理策略和自动化工作流。
sc-stripe
(STUB / NOT IMPLEMENTED YET) Stripe payments setup — create products/prices, webhook endpoint registration, customer portal config, restricted API keys. Pairs with sc-convex for `payments` table mutations and HTTP webhook routes.
download-platform-invoices
Harvest monthly SaaS billing invoices into normalized records and official PDF files.
nav-sop
Create Standard Operating Procedures after solving novel issues, establishing patterns, or documenting workflows. Use when user says "document this solution", "save this for next time", "create SOP".
stripe-money-ops
Irreversible Stripe money operations - refunds, payouts, transfers, subscription cancels, deletes. User-invoked only. This skill is intentionally excluded from automatic model invocation because these operations move real money and cannot be undone.
stripe-setup
Set up the stripe plugin. Use when the user asks to (1) configure Stripe accounts, (2) add or change Stripe API keys, (3) install the Stripe CLI, or (4) verify Stripe connectivity. Scaffolds the multi-account registry and provisions the bundled Stripe CLI.
research-pack
외부 공식문서·1차 자료·논문을 조사해 신뢰도 라벨이 붙은 리서치 노트를 작성한다. 기획 evidence 또는 구현 전 docs 확인용. (report + 노트 작성 전용 — 코드·기획 문서 수정 X)
company-enrichment
LeadMagic company search, filter search, funding, technographics, lookalikes, competitors, and company posts. Use when enriching a domain or company name, building company lists with typed filters, finding lookalike companies from a seed, researching an account's funding or tech stack, or pulling a company's recent public posts.
api-commerce-stripe
Stripe payment processing — Checkout Sessions, Payment Intents, subscriptions, webhooks, Connect, customer management, error handling
rn-publishing-payments
Use when preparing an Expo + RN app for store submission (metadata, screenshots, localized listings, privacy nutrition label, age rating) and integrating monetization (In-App Purchases via RevenueCat for digital goods/subscriptions; Stripe via WebView ONLY for non-digital services). Triggers on: "submit to App Store", "Play Store listing", "screenshot sizes", "RevenueCat setup", "Stripe payment in app", "subscription", "IAP", "privacy nutrition label", "App Store review reject". Not for: building / submitting (rn-eas-build-submit-update), backend setup (rn-backend).
stripe-api
Call any Stripe API endpoint. This skill should be used when the user asks to (1) read or look up any Stripe data (customers, charges, subscriptions, invoices, payment intents, balances, payouts, disputes, Connect accounts, Issuing, Treasury, Tax, Billing, Reporting, anything), (2) create or update Stripe objects, or (3) perform any Stripe operation by name. Covers the entire Stripe REST surface across all configured accounts.
creative-web
แนะนำ Design Style สำหรับเว็บไซต์ พร้อม Font Pairing (ไทย + อังกฤษ), Color Palette (hex) และเว็บอ้างอิงจริงให้เห็นภาพ — อิงจาก 20 สไตล์ชั้นนำ เช่น Minimal (Apple), Modern SaaS (Stripe), Glassmorphism (Linear), Dark Modern (Vercel), Luxury (Rolex), E-commerce (Nike) และอื่น ๆ ใช้ skill นี้ทันทีเมื่อผู้ใช้ถามเรื่อง design เว็บไซต์, landing page, web UI, สี, หรือ font เว็บ — เช่น "ทำเว็บ portfolio ใช้ style อะไรดี", "อยากได้เว็บแบบ Stripe", "landing page SaaS ใช้สีไหน", "ทำเว็บโรงพยาบาล", "เว็บ ecommerce ควร design ยังไง", "อยากได้ dark theme แบบ dev tool" — เรียกใช้ผ่าน `/creative:creative-web` เท่านั้น — ไม่ auto-trigger จากบทสนทนา
sales-adlynews
adly.news platform help — two-sided newsletter advertising marketplace connecting publishers with advertisers, featuring verified ESP metrics, in-app negotiation, ad slot management, and Stripe payments. Use when you want to list your newsletter on adly.news to attract sponsors, need help setting up ad slots with pricing and availability, want to browse and buy newsletter ad placements as an advertiser, trying to decide between adly.news and alternatives like Hecto or Paved for newsletter sponsorship, or wondering how to negotiate ad pricing with publishers on adly.news. Do NOT use for general newsletter monetization strategy (use /sales-newsletter) or sponsor intelligence and prospecting databases (use /sales-sponsorgap or /sales-whosponsorsstuff).
ai-citation-tracker
Track brand mentions, URL citations, and share-of-voice across the 2026 AI search surface — ChatGPT (with browsing), Perplexity, Claude (with search), Google Gemini, Google AI Overviews, Bing Copilot, You.com, Phind, and Microsoft Copilot..
revenue-gap-tracker
Track revenue monitoring gaps on ThumbGate.app - identify blocked data sources (gitignored business_os/, admin auth, Stripe env vars), audit available signals, and determine what is needed to move revenue monitoring from 3 to 5.
add-stripe
Use when user mentions Stripe, billing, subscriptions, plans, or payments - patterns for Stripe with price versioning and grandfathering
stripe-accounts
Inspect and switch Stripe accounts. Use when the user asks (1) which Stripe accounts are configured, (2) to switch the default account, (3) what mode an account is in, or (4) to check account setup. Read-only. Never prints secret keys.
stripe-multi-account
Run one Stripe read across many or all accounts and consolidate. Use when the user asks for a cross-account view, for example (1) total balances across all accounts, (2) all active subscriptions across the group, (3) every open dispute across accounts, or (4) compare a metric across businesses. Read-only by construction.
stripe-reports
Stripe reporting and financial summaries. Use when the user asks for (1) a Reporting API report run, (2) a Sigma-style financial summary, (3) payout or balance-transaction reconciliation, or (4) a cross-account revenue snapshot. Reads run immediately; creating a report run is mutating and is confirmed.
stripe-webhooks
Manage Stripe webhooks and CLI extras. Use when the user asks to (1) create, list, or delete webhook endpoints, (2) listen to live events locally, (3) trigger test events, or (4) tail API logs. Endpoint CRUD is REST and inherits the safety tier; listen and trigger use the bundled Stripe CLI.
accessibility
This skill should be used when building or reviewing UI for accessibility — keyboard navigation, screen readers, ARIA, color contrast, focus states, accessible forms, or WCAG compliance. Trigger phrases include "make it accessible", "a11y", "accessibility", "WCAG", "ARIA", "keyboard navigation", "screen reader", "color contrast", "focus states", "accessible form", "is this compliant", "EAA", "ADA". It targets WCAG 2.2 AA with concrete component rules and an axe-core test step.
api-design
This skill should be used when designing or building an API — endpoints, routes, request/response shapes, error formats, pagination, versioning, or deciding REST vs GraphQL. Trigger phrases include "design the API", "build an endpoint", "REST or GraphQL", "how should I structure my routes", "API error format", "paginate results", "version my API", "validate env vars", "idempotency", "what should this endpoint return". It applies proven REST conventions and a clear REST-vs-GraphQL decision, with env-config validation.
architecture-primer
This skill should be used when the user wants to design, plan, or decide the architecture of a system, app, or platform from scratch. Trigger phrases include "how do I structure this", "what architecture should I use", "how does this scale", "monolith or microservices", "what database", "what stack", "design the system", "how do I handle X users". Inspired by the System Design Primer. It runs a discovery phase, applies a decision tree, and outputs concrete architecture decisions with trade-offs.
auth
This skill should be used when adding authentication or authorization to an app or SaaS — login, signup, sessions, tokens, roles, permissions, multi-tenant access, SSO, or social login. Trigger phrases include "add login", "add auth", "sign in with Google", "protect this route", "user roles", "admin permissions", "JWT or sessions", "which auth provider", "RBAC", "multi-tenant access", "who can see what", "magic link", "SSO". It picks the right provider and pattern instead of rolling auth from scratch.
data-modeling
This skill should be used when designing a database schema, modeling data, choosing a database, planning migrations, or setting up multi-tenancy for a SaaS. Trigger phrases include "design the database", "model this data", "what database should I use", "schema for", "multi-tenant", "tenant isolation", "add an index", "how do I migrate", "SQL or NoSQL", "Postgres schema", "row level security", "RLS". It defaults to Postgres, models multi-tenancy safely, and enforces migration and indexing discipline.
design-taste-frontend
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
frontend-performance
This skill should be used when a frontend feels slow, fails Core Web Vitals, has a large bundle, or needs performance optimization. Trigger phrases include "make it faster", "improve performance", "Core Web Vitals", "LCP", "INP", "CLS", "reduce bundle size", "code splitting", "lazy load", "it's slow to load", "optimize images", "bundle too big", "Lighthouse score". It targets the real Core Web Vitals thresholds with stack-specific fixes for React + Vite + Vercel.
image-to-code
Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards, generate fresh standalone images for sections or detail views instead of cropping old ones, avoid lazy under-generation, avoid cards-inside-cards-inside-cards UI, and keep the hero clean, spacious, readable, and visible on a small laptop.
landing-page
This skill should be used when the user wants to create a landing page, sales page, home page, lead-capture page, or any conversion-oriented page. Trigger phrases include "build a landing page", "make a sales page", "create a home page for my product", "I need a page to sell X", "landing for my SaaS/course/service", "lead capture page". It asks up to 3 questions, applies a proven psychological section order, generates the copy, and produces ready-to-use components.
payments
This skill should be used when adding payments, subscriptions, billing, or pricing to a SaaS — Stripe integration, checkout, plans, the customer portal, webhooks, or deciding a pricing model. Trigger phrases include "add Stripe", "accept payments", "add a subscription", "charge users", "pricing tiers", "checkout", "billing portal", "handle the webhook", "set up plans", "monetize", "free trial". It wires Stripe correctly (checkout to webhook to fulfillment) and sets a sane pricing model.
pre-ship-security
This skill should be used right before deploying or shipping to production — a fast security review of the finished code, not a deep audit. Trigger phrases include "ready to ship", "before I deploy", "security check before launch", "is this safe to ship", "pre-launch checklist", "review security", "did I miss anything", "production-ready", "harden before launch", "antes de subir a producción". It runs npm audit + a secret scan, re-checks the code against the OWASP prevention checklist, and escalates to specialized audit tools only when the app is high-risk.
product-discovery
This skill should be used when the user has a product idea but is not sure what to build, what the MVP is, or where to start. Trigger phrases include "I have an idea for a product", "not sure what to build", "what should the MVP be", "where do I start", "is this idea any good", "help me scope this", "I want to build something but". Inspired by Design Sprint and Lean Startup. It separates the problem from the solution, validates the market, and defines a prioritized MVP.
pwa
This skill should be used when turning a web app into a Progressive Web App — making it installable, work offline, cache assets, or send push notifications. Trigger phrases include "make it a PWA", "installable app", "work offline", "offline mode", "service worker", "web push", "push notifications", "add to home screen", "app manifest", "cache assets", "make it feel like a native app". It sets up vite-plugin-pwa with the right caching strategy and avoids the stale-service-worker trap.
saas-router
This skill should be used FIRST whenever the user wants to create, build, design, ship, or prototype any digital product — a SaaS, web app, platform, MVP, landing page, sales page, dashboard, admin panel, backoffice, internal tool, API, database, auth, payments, or any user interface. Trigger phrases (English) include "build me a", "I want to create", "design a", "let's make a", "I have an idea for", "help me ship". Trigger phrases (Spanish) include "quiero construir", "armar una", "diseñar una", "hagamos un", "tengo una idea para", "necesito una app/SaaS/landing", "agregá login/pagos/base de datos", "subir a producción". It routes the request to the correct specialist skill instead of writing code or designing blindly.
secure-coding
This skill should be used while WRITING any backend, API, auth, or data-handling code for a web app or SaaS — to prevent vulnerabilities before they ship, not to audit them after. Trigger phrases include "add an endpoint", "handle user input", "store user data", "is this secure", "build the API", "save to the database", "handle the form", "user uploads", "process payment", "handle secrets", "set up CORS", "rate limit". It applies OWASP Top 10 prevention, input validation, secrets hygiene, and GDPR basics as you build.
technical-seo
This skill should be used when making a web app or SaaS discoverable and shareable — meta tags, OpenGraph/social previews, sitemap, robots.txt, structured data, or fixing the empty-HTML problem of a React SPA. Trigger phrases include "improve SEO", "add meta tags", "OpenGraph", "social share preview", "sitemap", "robots.txt", "structured data", "JSON-LD", "my page has no preview on Twitter/WhatsApp", "Google can't see my SPA", "prerender". It generates the head tags, files, and prerendering an SPA needs to be indexed and shared.
ui-design
This skill should be used when making visual design decisions, creating components, defining styles, colors, typography, spacing, or building any interface — including dashboards, admin panels, and web apps. Trigger phrases include "design the UI", "build a component", "pick colors", "create a design system", "make it look good", "style this", "dashboard layout", "make a dark mode". It generates a design system before writing code and avoids generic AI aesthetics.
skill-anything
Automatically generate production-ready Skills for any software, API, CLI tool, library, workflow, or service. Use this skill whenever the user wants to create a skill from scratch for a target application, convert an existing tool into an agent-native skill, generate skills for multiple platforms (Claude Code, OpenClaw, Codex), or automate the full skill creation pipeline including analysis, design, implementation, testing, optimization, and multi-platform packaging. Also use when the user mentions "skill-anything", "generate a skill for", "make a skill from", "skillify", or wants to turn any software into an agent-ready skill. Even if they just say "create a skill for X" where X is any tool or API, this skill should trigger.
combined-hubspot-stripe
Compare HubSpot open pipeline with Stripe paid invoices using Combined's granted datasets, explicit customer mapping, separate aggregation, and currency-aware time windows. Use for CRM and billing analysis without double-counting.
plan-testing
Use when an agent needs to design a comprehensive test strategy for a feature or refactor; identifies unit boundaries, mocks, and edge cases rather than writing the actual test code or executing test suites.
create-scraper
Given a careers page URL, uses Playwright browser tools to explore the page, identify reliable scraping patterns (preferring hidden JSON APIs over DOM scraping), then writes a TypeScript Scraper subclass for that company
clowk
Use when a prompt contains a $NAME placeholder clowk substituted for a credential, or when a command needs an API key, token, password or database URL clowk is holding. Explains how to use one without reading its value.
billing
Use for recurring revenue on Stripe — subscriptions, plans/tiers, trials, renewals, cancellation, proration, automated invoicing, usage-based/metered billing (Billing Meters), dunning/Smart Retries, the Customer Portal, and subscription tax basics. Triggers — "subscription", "recurring", "plan", "tier", "trial", "renewal", "cancel subscription", "proration/prorate", "upgrade/downgrade plan", "metered/usage-based billing", "billing meter", "meter event", "invoice/dunning/failed payment/retry", "customer portal", "subscription checkout", "Stripe Tax on subscriptions". Not for one-time payments (see stripe-suite:payments) or marketplace payouts (see stripe-suite:connect). API version pinned 2026-06-24.dahlia.
integration
Use this FIRST for ANY Stripe integration to pick the right approach before writing code. Router that classifies the ask (accept a one-time payment, subscriptions/recurring/invoicing, in-person/POS, marketplace/platform payouts, fraud/identity/bank-linking) and routes to the correct sibling skill and integration surface (Payment Links, Checkout, Elements, mobile/Terminal SDKs). Triggers — "Stripe", "accept a payment", "PaymentIntent", "checkout", "subscription/recurring/plan/trial/metered billing", "invoice", "marketplace/platform/Connect/split funds/payout", "Terminal/card reader/POS/Tap to Pay", "webhook/Stripe-Signature", "test cards/Stripe CLI", "publishable/secret/restricted key", "idempotency key". API version pinned 2026-06-24.dahlia.
payments
Use to accept a ONE-TIME / on-demand payment for your own business with Stripe — the PaymentIntent-based flow and the four surfaces that sit on top of it. Covers choosing between Payment Links (no-code), Checkout Sessions (low-code, Stripe's default), Payment Element / Elements (custom UI), and raw PaymentIntents (max control); the PaymentIntent lifecycle & statuses; automatic vs manual (authorize-then-capture) capture; SCA / 3D Secure handling; and refunds vs cancel. For recurring charges route to stripe-suite:billing; for marketplace payouts route to stripe-suite:connect; for the authoritative fulfilment signal route to stripe-suite:webhooks. Triggers — "accept a payment", "one-time payment", "PaymentIntent", "client_secret", "confirm payment", "Checkout Session", "Payment Element", "Elements", "Payment Link", "capture / manual capture / authorize", "requires_action / requires_capture", "3D Secure / 3DS / SCA / next_action", "refund / cancel a payment". API version pinned 2026-06-24.dahlia.
terminal
In-person / point-of-sale payments with Stripe Terminal — physical card readers and Tap to Pay. Use when the ask is about accepting a card present, a countertop or handheld reader, or turning a phone into a reader. Triggers — "Stripe Terminal", "card reader", "POS", "point of sale", "in-person payment", "card present / card_present", "process_payment_intent", "connection token", "Tap to Pay on iPhone/Android", "WisePOS E", "Stripe Reader S700 / S710 / T600", "reader location", "simulated reader", "on-reader tipping", "offline mode", "in-person / Interac refund". Reached from the stripe-suite:integration router when the flow is in-person. API version pinned 2026-06-24.dahlia.
stripe-japan-agent
Payment management for Japan — PayPay, konbini payments, subscriptions, invoicing via Stripe
drive-logged-in-chrome
Drive Igor's already-authenticated Google Chrome via AppleScript for login-walled dashboards (Stripe Payment Links, Apollo web, Play Console, LinkedIn, ASC). NEVER use Playwright MCP as the source of truth for "am I logged in?" — Playwright is a separate browser profile without Chrome cookies. Trigger when: Stripe, payment links, buy.stripe.com, dashboard.stripe.com, "logged into Chrome", login wall, Playwright got login page but user says they're signed in, Apollo web UI, or any task needs the real Chrome session. Slash: /drive-logged-in-chrome. Cross-ref: use-existing-browser-sessions.
execute-revenue-cash-path
Execute the real cash path for mac-yolo-safeguards / ThumbGate: diagnose funnel, Apollo enrich, Gmail send, live Stripe links from Chrome, pipeline-update, never ship theater. Trigger when: make money, make money today, do everything, cash, revenue, sell, close, outreach, pipeline stuck, $0 revenue, Partner Pilot, diagnostic $499, hardening $1500, or when tempted to build another sales tool instead of sending. Slash: /execute-revenue-cash-path. Do NOT invoke for pure product engineering without a revenue ask.
secrets
How to use passwords, SSH credentials, API keys and tokens without them entering the conversation. Use whenever a task needs a credential — connecting to a server over SSH/SCP/rsync, logging into a database or panel, calling an authenticated API, or when a command fails with a permission/authentication error. Also use when the user offers to give you a password, or when a command would print a credential.
account-research
Produce a high-signal intelligence brief on a target company using Explorium firmographics, technographics, funding, hiring and challenge signals, business events, recent website and LinkedIn moves, plus a peer cohort. Identify the account by Explorium business_id (preferred) or by company name or domain (which triggers a match step). Always lead with a TL;DR framed by the user's stated research purpose (QBR prep, competitive analysis, cold outbound, renewal risk, expansion).
enrich-company
Pull a single company's full profile in Explorium. Accepts a domain, company name, or business_id and returns firmographics, technographics, financial metrics, funding history, workforce trends, competitive landscape, and the contact pool count.
comprehensive-enrichment
Use this skill when the user wants to enrich, look up, or research a lead, contact, person, or company — from an email, name, LinkedIn URL, domain, or company name. Triggers on "enrich this lead", "look up John at Stripe", "who is john@stripe.com", "research stripe.com", "profile this company", "find emails and phone for", "company funding and competitors". Resolves contact info, verified work emails, phone, social profiles, company overview, funding, products, and competitors across many MPP data providers (Apollo, Hunter, Clado, Abstract Company Enrichment, Diffbot KG, Exa, Firecrawl). Every provider call is through the SELAT Router (MPP).
email-campaign
Use this skill when the user wants to build a verified cold-email or outreach list — e.g. "build an email campaign", "find and verify emails for a domain", "find someone's work email", "verify these emails before I send", "enrich a lead for personalized outreach", "get company brand context for outreach". Runs a 7-step pipeline across MPP merchants (Fiber company search, Hunter domain/email lookup + verification + bounce check, Apollo lead enrichment, Abstract Company Enrichment company context), all through the SELAT Router.
enrich-waterfall
Use this skill when the user wants to enrich a person or company from a partial identifier — e.g. "enrich this email", "find the work email and phone for X at Y", "who is this person", "build a lead profile for stripe.com", "company enrichment for this domain", "find their LinkedIn / Twitter", "get me funding and hiring signals", "waterfall enrichment", "verify this email". Runs a cheapest-first B2B enrichment waterfall — resolve the person sub-cent, anchor the company, fan out to signals / social, escalate to premium contact reveals (Clado contacts, Clado people search) only on gaps, then verify the email. Nearly every step is paid MPP on Tempo through the SELAT Router; the SELAT-native X/Twitter step is a x402 via Circle Gateway call via the SELAT Router. The selat CLI compiles each manifest step into a payment.
lead-enrichment
Use this skill when the user wants to enrich a sales lead or contact across multiple data sources — e.g. "enrich this lead", "find and verify their work email", "get a phone number for this prospect", "enrich the company", "complete contact data for John Doe at Stripe". Chains three MPP on Tempo merchants across five steps (Hunter for email find/verify and company enrichment, Apollo for lead enrichment, Clado for phone/contact discovery) in a single run, all paid through the SELAT Router (MPP on Tempo rail).
sales-prospecting
Use this skill when the user wants to build a B2B prospect or lead list with verified contact info — e.g. "build a prospect list", "find decision makers at these companies", "get verified emails for this domain", "find the CTO's email and verify it", "sales prospecting", "lead enrichment for outreach". Runs a MPP on Tempo pipeline — company search (Fiber), people search (Fiber), domain email lookup (Hunter), specific-contact email (Hunter email finder), email verification (Hunter email verifier), and company enrichment (Abstract Company Enrichment), all paid through the SELAT Router.
n8n-workflow-patterns
Proven workflow architectural patterns from real n8n workflows. Use when building new workflows, designing workflow structure, choosing workflow patterns, planning workflow architecture, or asking about webhook processing, HTTP API integration, database operations, AI agent workflows, batch processing, or scheduled tasks. Always consult this skill when the user asks to create, build, or design an n8n workflow, automate a process, or connect services — even if they don't explicitly mention 'patterns'. Covers webhook, API, database, AI, batch processing, and scheduled automation architectures.
stripe-best-practices
Best practices for building Stripe integrations. Covers payment processing, checkout flows, subscriptions, webhooks, Connect platforms, and Stripe API usage.
karpathy-verification
Use when judging whether output is correct or finished: reviewing an AI-written diff before accepting, merging, or shipping; deciding whether a working demo means done; checking a model's numbers, counts, or self-reported success; or setting up an LLM as a judge, grader, or council.
extension-payment
Integrate payment gateways into Chrome extensions. Stripe, Paddle, Lemon Squeezy, Polar, PayPal, and more. Licensing, subscriptions, freemium. Use when: payment, monetize, subscribe, billing, premium.
upgrade-stripe
Guide for upgrading Stripe API versions and SDKs
stripe-best-practices
Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial accounts, integration surfaces (Checkout, Payment Element), and migrating from deprecated Stripe APIs. Use when building, modifying, or reviewing any Stripe integration — including accepting payments, building marketplaces, integrating Stripe, processing payments, setting up subscriptions, or creating connected accounts.
stripe-projects
Use when setting up a new app or local repo with Stripe Projects, provisioning a software stack, or bootstrapping the Projects CLI from a coding agent.
Integration detected automatically from skill content. Some results may be false positives.