New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Stripe Apps

by fossasia in 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.

Apache-2.0Auto-check passedBackend & APIs

Install Stripe Apps

skills CLI
$ npx skills add fossasia/eventyay --skill stripe-apps -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install fossasia/eventyay stripe-apps --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/fossasia/eventyay.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/stripe-apps .claude/skills/stripe-apps && rm -rf skills-src

Use ~/.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/

Facts

Skill name
stripe-apps
GitHub stars
1.7k
Used in
1 other repo
Token cost
~3.6k tokens
SKILL.md length
1,692 words
Files
13 (incl. references)
Skills in repo
21
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when building, modifying, or reviewing a Stripe App — or when the user describes something that implies one (e.g.

  • Works in 5 steps: Discovery (your first message) → Scaffold → Build (WRITE every file to disk) → …
  • Reviewing a Stripe App —
  • SKILL.md covers Stripe Apps — Agent Instructions, HARD RULES — violating any of…, BLOCKED — these produce broken… and Protocol — execute these steps…, plus 2 more sections
  • Calls stripe and pnpm

What it does

Stripe Apps is an agent skill from fossasia/eventyay. Use when building, modifying, or reviewing a Stripe App — or when the user describes something that implies one (e.g. "add a panel to the customer page", "customize my Stripe Dashboard", "react to Stripe events from my app", "connect my service to Stripe without sharing API keys"). Covers the full app development workflow (scaffold, preview, upload, versioning), UI extension architecture (sandboxed iframe, Stripe UI toolkit, viewports), extension types (UI extensions, backend-only, extension interfaces, embedded…

Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including reference files (for example `references/authentication.md`, `references/backend.md` and `references/canonical-docs.md`).

It sits in Backend & APIs, covering Webhooks. It works with Stripe and React. The repository describes itself as: Open Source Event Management, Ticketing and Checkins, Talks and Schedules, Video and Interpretations, Badges, Exhibitions and more https://eventyay.com. The licence is Apache-2.0.

When your agent uses it

  • Reviewing a Stripe App —
  • The user describes something that implies one (e.g
  • The user mentions Stripe Apps
  • @stripe/ui-extension-sdk

Example prompts

  • “add a panel to the customer page”
  • “customize my Stripe Dashboard”
  • “react to Stripe events from my app”
  • “/stripe-apps”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Discovery (your first message)
  2. Scaffold
  3. Build (WRITE every file to disk)
  4. Deliver (REQUIRED — do not skip)
  5. Verify files exist

What it can do on your machine

Read from SKILL.md and the folder at commit b539d59. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    Shell commands in SKILL.md call:

    • stripe
    • pnpm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.stripe.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Stripe Apps loads about 3.6k tokens when it runs, and up to ~23k if it reads all its reference files. Until then it costs about 257 tokens; SKILL.md has 1,692 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~257
When it runs · the whole SKILL.md, loaded when a task matches
~3.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~23k

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.

Safety

Auto-check passed

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from fossasia/eventyay at commit b539d59, republished under its Apache-2.0 licence (© fossasia). 1,692 words, ~3,586 tokens.

Download SKILL.mdSave it as .claude/skills/stripe-apps/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.
name
stripe-apps
description
Use when building, modifying, or reviewing a Stripe App — or when the user describes something that implies one (e.g. "add a panel to the customer page", "customize my Stripe Dashboard", "react to Stripe events from my app", "connect my service to Stripe without sharing API keys"). Covers the full app development workflow (scaffold, preview, upload, versioning), UI extension architecture (sandboxed iframe, Stripe UI toolkit, viewports), extension types (UI extensions, backend-only, extension interfaces, embedded apps), authentication (platform keys, OAuth, restricted API keys), stripe-app.yaml manifest setup (permissions, viewports, CSP), webhook configuration for apps, Secret Store API, `fetchStripeSignature` auth, and marketplace publishing, plus submitting one agentic feedback report after a build. Use when the user mentions Stripe Apps, UI extensions, @stripe/ui-extension-sdk, @stripe/extensibility-sdk, script extensions, stripe-app.yaml, Dashboard extensions, or customizing the Stripe Dashboard.

Stripe Apps — Agent Instructions

FIRST ACTION: Say “Loading Stripe Apps skill.” then Read references/discovery.md. This file has routing logic you need before asking the user questions.

Your role

You are a PROJECT BUILDER and INSTRUCTOR. Your primary output is working files on the user’s machine that they can run immediately. If you explain code without also writing it to disk using your Write tool, the user has nothing they can execute.

You are also a patient guide. Many users have never heard of Stripe Apps, viewports, or webhooks. When they say “I’m not sure” or “what does that mean?”, explain concepts in plain language with examples from their specific idea.

Your tool calls (Read, Write) are your real work. Your chat messages explain what you did and teach the user why.

Source of truth for code patterns

Your training data for Stripe Apps SDK patterns may be outdated or incorrect. Before writing any code file, you MUST read the relevant canonical docs page using WebFetch. See references/canonical-docs.md for the full list of docs pages.

If you cannot access the docs, tell the user: “I need to check the current Stripe Apps documentation to write correct code. Can you provide the current patterns from [relevant docs URL], or shall I proceed with the scaffold and you can verify against the docs?”

HARD RULES — violating any of these is a failure

#RuleWhat failure looks like
0BEFORE ANYTHING ELSE: (1) Say “Loading Stripe Apps skill.” (2) Call Read on references/discovery.md to load the routing table. You need this data before you can ask informed questions.Responding to the user before calling Read on discovery.md
1After reading discovery.md, your FIRST message to the user is ONLY the 4 discovery questions (see Step 1). No code, no plan, no summary. Even if the user’s request already mentions details — ask anyway. Users have unstated requirements that only emerge through questions.Presenting a summary, plan, or any code before asking questions 1-4 and getting answers
2You MUST use your Write tool to create or modify files on disk. The scaffold creates base files via CLI — after that, use Write to modify scaffolded files and create new ones. A response with code only in chat gives the user nothing runnable.Producing code in chat without calling Write to save it to disk
3Run stripe generate app <name> using your Bash tool to scaffold the project. Then use Write to modify scaffolded files and create additional files the app needs.Writing stripe-app.yaml or package.json from scratch instead of modifying the scaffold output
4Before writing code for any topic (backend, UI, webhooks, auth), read the relevant canonical docs page using WebFetch. See references/canonical-docs.md. The docs are the source of truth — not this skill file, not your training data.Writing code from memory without checking the current docs
5Tell user: stripe apps upload BEFORE testing fetchStripeSignature/Secret Store (the signing secret is generated during first upload).Omitting upload-first requirement
6File names: ui/src/views/App.tsx (V2 workspace layout), server.js (project root). Only create files that are needed for the app’s architecture (see Step 3).Using wrong filenames or creating files the architecture doesn’t need
7Every file you write to disk MUST be complete and runnable — not a skeleton or placeholder. The user should be able to run it immediately. Do not write partial files with TODOs.Writing a file with TODO placeholders or incomplete implementations
8When presenting the development workflow, include pnpm build and pnpm test as explicit steps for apps with a UI extension. Backend-only apps without TypeScript skip pnpm build.Omitting build/test steps for UI apps, or requiring them for backend-only apps
9If the user’s app requires custom objects or extension interfaces (private preview features), inform them the feature is in private preview and ask them to confirm they have access BEFORE proceeding. Do not silently proceed with a private preview feature.Building with private preview features without confirming user has access
10Before ending the conversation, if you ran any toolchain command this session, submit exactly one stripe feedback report — see references/feedback.md. Never block delivery on it.Ending a build session in which commands were run without submitting one feedback report

BLOCKED — these produce broken apps

BLOCKED (never use)Use instead
stripe apps createstripe generate app <name>
Raw HTML in UI extensions (<div>, <span>, <p>, <button>, <input>, <h1>-<h6>)SDK components from @stripe/ui-extension-sdk/ui (Box, Inline, Button, TextField, etc.)
CSS frameworks in UI (Tailwind, MUI, Bootstrap, styled-components, CSS files)Only @stripe/ui-extension-sdk/ui components — no custom styling
React 18+ APIs in UI (useId, useDeferredValue, useTransition, concurrent features)React 17 hooks only (Stripe Apps run React 17.0.2)
window, document, localStorage, sessionStorage in UINot available in sandboxed iframe

Protocol — execute these steps IN ORDER

Step 1 — Discovery (your first message)

Read references/discovery.md using your file-reading tool.

You CANNOT determine the correct architecture without user input because:

  • The authentication type determines the backend pattern (platform keys vs OAuth vs restricted keys)
  • Private vs public apps have different webhook configurations
  • The viewport determines which context props are available
  • Backend vs frontend-only changes which files you create

Ask these questions in your FIRST message — nothing else:

  1. What should the app do? (UI in Dashboard / react to events / both / modify billing or payment logic)
  2. Where should it appear? (customer detail, payment detail, full page, etc.)
  3. Who is it for? (only you or your team = private, OR other Stripe users = public/marketplace)
  4. Does it need to store data or talk to other services?

Do NOT include a summary, plan, or architecture in this first message. ONLY the 4 questions above.

If the user doesn’t know an answer or asks for clarification:

  • Explain the concept in plain language
  • Give concrete examples from their stated idea
  • Help them figure out the right answer

Private preview check: After getting answers, before showing your summary, check whether their app implies needing:

  • Custom objects (storing custom data models IN Stripe)
  • Extension interfaces (changing how Stripe processes billing, payments, or tax)

If yes: tell the user that feature is in private preview, ask them to confirm access. See references/discovery.md for exact wording and alternatives.

Full-page apps require @stripe/ui-extension-sdk version 9.2.1 or later and the latest version of the Stripe Apps CLI plugin.

After the user answers, show a plain-language summary:

  • “You want to: [goal]. It will appear: [where]. It’s for: [private/marketplace]. It needs: [backend/secrets/only Stripe data].”

Wait for explicit confirmation before proceeding.

Show full SKILL.md (623 more words)Show less
Step 2 — Scaffold

Run the scaffold command yourself using your Bash tool:

bash
stripe generate app <name>

This creates a V2 workspace: stripe-app.yaml, package.json, pnpm-workspace.yaml, ui/src/views/App.tsx.

After the scaffold completes, proceed directly to Step 3.

Step 3 — Build (WRITE every file to disk)

Before writing any code, read the relevant canonical docs pages (see references/canonical-docs.md) using WebFetch:

  • For UI code: read the Extensions SDK API page and the UI components page
  • For backend code: read the Backend + signed requests page and Authentication types page
  • For webhooks: read the Events page
  • For Secret Store: read the Secret Store page

YOUR PRIMARY JOB: Create files on disk following the patterns from the docs.

Which files to create depends on discovery answers:

ArchitectureFiles to write
Frontend-only (reads Stripe data, no external services)Modify: stripe-app.yaml, ui/src/views/App.tsx
Backend-only (webhooks/events, no Dashboard UI)Modify: stripe-app.yaml. Create: server.js
Full-stack (UI + backend)Modify: stripe-app.yaml, ui/src/views/App.tsx. Create: server.js
Script extensionGenerate the extension, then implement its source, configuration, and tests.

For each file: call your Write tool FIRST, then explain what it does.

Key constraints for UI code:

  • Import ONLY from @stripe/ui-extension-sdk/ui for components
  • NO raw HTML elements, NO CSS
  • Follow the SDK API patterns from the canonical docs exactly

Key constraints for backend code (server.js):

Key constraints for stripe-app.yaml:

Step 4 — Deliver (REQUIRED — do not skip)

Your FINAL message MUST present the development workflow:

  1. stripe generate app <name> → scaffold
  2. pnpm install → dependencies
  3. Modify scaffolded files + create additional files → implement
  4. pnpm build → compile TypeScript (UI and script extensions)
  5. pnpm test → run unit tests
  6. stripe apps start → local preview for Dashboard UI extensions
  7. stripe apps upload → publish version (required before fetchStripeSignature or Secret Store)
  8. Install from Dashboard → test

Important workflow facts:

  • Use sandboxes for safe testing — they provide isolated environments for app development
  • stripe apps upload generates the signing secret needed for fetchStripeSignature
  • Public/marketplace apps need account activation (verified email + business details)
  • For webhook forwarding during local dev, see references/webhooks.md
Step 5 — Verify files exist

Before ending the conversation, confirm your files are on disk. Run ls on the files you wrote to verify they exist.

If any file is MISSING, call Write now to create it.

Troubleshooting uploads

ErrorCauseFix
Invalid manifestMissing required fields or malformed YAMLCheck indentation; ensure id:, version:, name: are present
Build failedUI component has type/import errorsRun pnpm build locally first
Version already existsAlready uploaded this version numberBump version in stripe-app.yaml
Permission deniedCLI not logged in or wrong accountRun stripe login
connect-src / CSP errorApp calls undeclared URLAdd URL to content_security_policy.connect-src
extensions field requiredMissing extensions: []Add extensions: [] to stripe-app.yaml
Component not foundViewport references wrong component nameMatch component: value to your default export

Reference files

FileRead when
references/canonical-docs.mdALWAYS — lists docs pages to WebFetch before writing code
references/discovery.mdALWAYS FIRST — full discovery script with routing
references/backend.mdBefore writing server.js
references/ui-extensions.mdBefore writing React/UI code
references/workflow.mdFull development loop with all CLI commands
references/extension-types.mdAfter discovery — map answers to extension type
references/script-extensions.mdWhen authoring a script extension: generation, SDK contracts, runtime, configuration, and tests
references/webhooks.mdWhen app reacts to Stripe events
references/authentication.mdFor auth type selection and patterns
references/onboarding-ux.mdFor first-run experience
references/publishing.mdFor marketplace publishing
references/feedback.mdAfter a build where you ran CLI/build commands — submit one feedback report

© fossasia, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 12 other files (references) in .agents/skills/stripe-apps of fossasia/eventyay.

  • SKILL.md
  • references/authentication.md
  • references/backend.md
  • references/canonical-docs.md
  • references/discovery.md
  • references/extension-types.md
  • references/feedback.md
  • references/onboarding-ux.md
  • references/publishing.md
  • references/script-extensions.md
  • references/ui-extensions.md
  • references/webhooks.md
  • references/workflow.md

Open the folder on GitHubat commit b539d59

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in fossasia/eventyay, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Stripe Apps 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.

Stripe Apps compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Stripe Apps this skillfossasia/eventyay1.7k1 repos~3.6kAutomated safety check: PassApache-2.0
Stripe Best Practiceskanchengw/cnllm1732 repos~925Automated safety check: PassApache-2.0
Cashier Stripe Developmentluadotsh/lua3431 repos~1.2kAutomated safety check: PassMIT
Stripe Integrationwshobson/agents40k10 repos~1kAutomated safety check: PassMIT
Convex HTTP Actionswaynesutton/builder-skills406—~2.6kAutomated safety check: PassApache-2.0
Integrating Stripe Webhookspr-pm/prpm1221 repos~1.8kAutomated safety check: PassMIT

Similar skills

  • Stripe Best Practices

    kanchengw/cnllm

    Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial…

    173 GitHub starsUsed in 2 repos~925 tokens
    Backend & APIsAuto-check passed

  • Cashier Stripe Development

    luadotsh/lua

    Handles Laravel Cashier Stripe integration including subscriptions, webhooks, Stripe Checkout, invoices, charges, refunds, trials, coupons, metered billing, and payment failure handling.

    343 GitHub starsUsed in 1 repo~1.2k tokens
    Backend & APIsAuto-check passed

  • Stripe Integration

    wshobson/agents

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

    40k GitHub starsUsed in 10 repos~1k tokens
    Backend & APIsAuto-check passed

  • Convex HTTP Actions

    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.

    406 GitHub stars~2.6k tokensUpdated 12 days ago
    Backend & APIsAuto-check passed

  • Integrating Stripe Webhooks

    pr-pm/prpm

    A skill your agent uses when implementing Stripe webhook endpoints and getting 'Raw body not available' or signature verification errors - provides raw body parsing solutions and subscription period…

    122 GitHub starsUsed in 1 repo~1.8k tokens
    Backend & APIsAuto-check passed

  • cmux Billing Runbook

    manaflow-ai/cmux

    Runbook for the cmux billing code: Stripe Checkout, customer portal, subscription changes, webhooks and how Pro plan entitlement is resolved from Stack metadata.

    28k GitHub stars~2.8k tokensUpdated today
    Backend & APIsAuto-check passed

More from fossasia/eventyay

All 21 skills in this repo

  • Stripe Projects

    fossasia/eventyay

    A skill your agent uses when the user wants to provision infrastructure or third-party services using Stripe Projects.

    1.7k GitHub starsUsed in 5 repos~2k tokens
    Auto-check: notes

  • Connect Recommend

    fossasia/eventyay

    A skill your agent uses when the user asks about Stripe Connect configuration, charge patterns, Dashboard access, or how to get started with Connect, is building a marketplace, platform…

    1.7k GitHub starsUsed in 1 repo~5.9k tokens
    Auto-check: warnings

  • Django Run Locally

    fossasia/eventyay

    Steps for initiating the Django development server without Docker

    1.7k GitHub stars~411 tokensUpdated today
    Auto-check passed

  • Docker Deployment

    fossasia/eventyay

    Docker Compose, container services, deployment. An agent skill from fossasia/eventyay.

    1.7k GitHub stars~574 tokensUpdated today
    Auto-check: notes

  • Stripe Best Practices

    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)…

    1.7k GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed

  • Repo Navigation

    fossasia/eventyay

    Repository layout and where to find code. An agent skill from fossasia/eventyay.

    1.7k GitHub stars~752 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Stripe Apps

What does Stripe Apps do?

A skill your agent uses when building, modifying, or reviewing a Stripe App — or when the user describes something that implies one (e.g. Stripe Apps is an agent skill from fossasia/eventyay.g.

When should I use Stripe Apps?

Stripe Apps fits situations like: reviewing a Stripe App —; the user describes something that implies one (e.g; the user mentions Stripe Apps; @stripe/ui-extension-sdk.

How do I install Stripe Apps in Claude Code?

Run `npx skills add fossasia/eventyay --skill stripe-apps -a claude-code`. Or copy the skill folder (.agents/skills/stripe-apps in fossasia/eventyay) into .claude/skills/stripe-apps in your project. Claude Code loads it when a task matches its description.

How do I install Stripe Apps in Codex?

Run `npx skills add fossasia/eventyay --skill stripe-apps -a codex`. Or copy the skill folder (.agents/skills/stripe-apps in fossasia/eventyay) into .agents/skills/stripe-apps in your project. Codex loads it when a task matches its description.

Can I use Stripe Apps in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add fossasia/eventyay --skill stripe-apps -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-apps, .gemini/skills/stripe-apps, .github/skills/stripe-apps and .opencode/skills/stripe-apps in your project.

What does Stripe Apps need to run?

Going by SKILL.md and its folder, Stripe Apps needs the command-line tools its instructions call (stripe and pnpm).

Does Stripe Apps access the network?

SKILL.md names 1 domain. As links in the text: docs.stripe.com. This is read from the text; nothing was executed.

Is Stripe Apps safe to install?

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. Review the folder before installing.

What licence does Stripe Apps use?

Stripe Apps is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Stripe Apps use?

About 3.6k tokens (SKILL.md is roughly 14k 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 19k tokens, read only when the agent opens those files.

What are the alternatives to Stripe Apps?

Skills that share tags, products or a category with Stripe Apps: Stripe Best Practices (kanchengw/cnllm, 173 stars), Cashier Stripe Development (luadotsh/lua, 343 stars), Stripe Integration (wshobson/agents, 40k stars) and Convex HTTP Actions (waynesutton/builder-skills, 406 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Stripe Apps?

fossasia (a GitHub organization) maintains it in fossasia/eventyay, which has 1,702 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 9, 2026.

Source: fossasia/eventyay on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.