Individual skill
stripe-apps
Build, modify, or review Stripe Apps and extensions using the relevant documentation and reference guides. Use for custom Stripe Dashboard UI, stripe-app.yaml, @stripe/ui-extension-sdk, @stripe/extensibility-sdk, script extensions, extension interfaces, custom workflow actions, and apps that authenticate to Stripe or react to events. Also use when deciding whether a Stripe extension can support the user's billing or workflow requirements.
providers/cursor/plugin/skills/stripe-apps/SKILL.md
Source commit 38fa04542e4d8f41e5ee4349a141ac308a0c26d1
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 2,051
- Repository last updated
- Nov 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- llm Repository topic
- llm-agents Repository topic
- python Repository topic
- typescript Repository topic
- workflows Repository topic
- mcp Repository topic
- ai Repository topic
- gemini-cli-extension Repository topic
- design Derived category
- operations Derived category
- docs Derived category
- engineering Derived category
- design-interface Derived category
- engineering-web Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 7,764 bytesreferences/authentication.mddoc · 4,746 bytesreferences/backend.mddoc · 4,457 bytesreferences/canonical-docs.mddoc · 4,478 bytesreferences/discovery.mddoc · 9,445 bytesreferences/extension-types.mddoc · 5,245 bytesreferences/feedback.mddoc · 1,977 bytesreferences/onboarding-ux.mddoc · 2,732 bytesreferences/publishing.mddoc · 5,877 bytesreferences/script-extensions.mddoc · 7,512 bytesreferences/ui-extensions.mddoc · 21,180 bytesreferences/webhooks.mddoc · 3,436 bytesreferences/workflow.mddoc · 8,504 bytes
Read excerpt
## Stripe Apps
Select and read the existing guidance for the user’s task. Product documentation describes what an extension can do; implementation guides describe how to build it. Before recommending an extension or writing code, load the applicable bundled reference files as well as the relevant product documentation. A link or filename in this skill isn’t a substitute for reading its contents.
For a capability question, check native Stripe features and the documented applicability and limitations of the extension. For an implementation request, create or modify working files using the selected guide. For an existing app, inspect its manifest, packages, installed SDK, and local agent instructions before deciding what to change.
## Choose the relevant documentation
Use information already supplied by the user or existing app. Read <references/discovery.md> when you need to clarify the app’s requirements, and <references/extension-types.md> for an overview of app architectures. Ask only for missing information that affects the task.
### Product capabilities
Use these existing product documents to determine which capability fits and whether the account has the required access. Don’t infer support from an extension’s name or the existence of a scaffold.
