Stripe Local Dev
ListedSimulates Stripe payment flows locally for development and testing without real transactions.
Install on your platform
stripe-local-dev. phrazzld/claude-config is deleted or private, so it cannot be installed from.We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-22. We don't show a command we know will fail.
What we know about this skill
Publisher
phrazzld
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
We could not read this skill's source, so none of the checks below were run.
About this skill
What it does
This skill, stripe-local-dev, provides a local development environment for Stripe. It allows you to simulate Stripe's API and webhooks locally, enabling faster iteration during development without relying on live test data or incurring real charges. This is particularly useful for building integrations and testing payment flows in isolation. The skill streamlines the setup process, reducing configuration overhead.
When to use it
- Developing a new application that integrates with Stripe.
- Debugging issues related to Stripe webhooks or API calls.
- Testing different Stripe scenarios without using live test data.
- Creating reproducible development environments for teams working on Stripe integrations.
- Experimenting with Stripe's features in a safe, isolated environment.
Key capabilities
- Local Stripe API simulation
- Webhook event handling and replay
- Simplified setup and configuration
- Isolated development environment
Example prompts
- "Start the local Stripe development server."
- "Simulate a successful payment of $10 using test card X."
- "Replay the last webhook event I received from Stripe."
Tips & gotchas
- Ensure you have Node.js and npm installed, as this skill likely utilizes JavaScript-based tooling for local server setup.
- The specific commands to interact with the simulated environment may vary depending on the underlying implementation; consult any accompanying documentation or instructions provided by the author.