
Stripe Projects
- 27 installs
- stripe/com
stripe-projects provisions services via Stripe Projects CLI.
About
The stripe-projects skill verifies providers on projects.dev, installs Stripe CLI 1.40+ and projects plugin, searches catalog, initializes projects, and retrieves API keys with platform-specific install instructions.
- projects.dev provider directory verification.
- Stripe CLI and plugin version gates.
- stripe projects search and init.
- Cross-platform CLI install paths.
- Stops if provider not in catalog.
Stripe Projects by the numbers
- 27 all-time installs (skills.sh)
- +1 installs in the week ending Jul 20, 2026 (Skillselion tracking)
- Ranked #1,244 of 2,719 Automation & Workflows skills by installs in the Skillselion catalog
- Data as of Jul 20, 2026 (Skillselion catalog sync)
stripe-projects capabilities & compatibility
- Capabilities
- provisioning workflow
- Works with
- stripe
- Use cases
- api development
npx skills add https://github.com/stripe/com --skill stripe-projectsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 27 |
|---|---|
| Repository | stripe/com ↗ |
How do I provision a projects.dev service?
Provision projects.dev services via Stripe Projects CLI catalog search and init.
Who is it for?
Developers using projects.dev service catalog.
Skip if: Skip for direct vendor signup.
When should I use this skill?
projects.dev or service API key provisioning request.
What you get
Stripe project with service credentials.
Files
Stripe Projects — Service Provisioning
Provision third-party services and retrieve API keys/tokens using the Stripe Projects CLI plugin.
Workflow
Step 1: Verify Provider Availability
Before doing anything else, fetch https://projects.dev/providers and check whether the requested provider appears in the directory listing.
- If the provider isn’t listed on that page, inform the user that Stripe Projects doesn’t support this provider and stop.
- If the provider is listed, continue.
Step 2: Ensure Stripe CLI is Installed
Check if the Stripe CLI is available:
which stripe && stripe --versionIf not installed, install based on the user’s platform:
macOS (Homebrew):
brew install stripe/stripe-cli/stripeLinux (Debian/Ubuntu via APT):
curl -s https://packages.stripe.dev/api/security/keypair/stripe-cli-gpg/public | gpg --dearmor | sudo tee /usr/share/keyrings/stripe.gpg > /dev/null
echo "deb [signed-by=/usr/share/keyrings/stripe.gpg] https://packages.stripe.dev/stripe-cli-debian-local stable main" | sudo tee -a /etc/apt/sources.list.d/stripe.list
sudo apt update
sudo apt install stripeWindows (Scoop):
scoop bucket add stripe https://github.com/stripe/scoop-stripe-cli.git
scoop install stripeIf installed, but the version is lower than 1.40.0, then upgrade based on the user’s platform:
macOS (Homebrew):
brew upgrade stripe/stripe-cli/stripeor follow instructions at https://docs.stripe.com/stripe-cli/upgrade for other platforms.
Step 3: Ensure Stripe Projects Plugin is Installed and on Latest
stripe plugin install projectsStep 4: Search the Catalog
Confirm the specific provider is available and validates the specific service:
stripe projects search <query> --jsonIf result_count is 0, inform the user the service was not found in the catalog and stop.
Step 5: Initialize a Project
Check if a project is already initialized:
stripe projects status --jsonIf not initialized:
stripe projects init --json --yesNote: If the user hasn’t logged in to the Stripe CLI, projects init will redirect them to a browser to either log in to an existing Stripe account or create a new Stripe Projects account. When this happens, prompt the user:
▎ Stripe Projects is redirecting you to the browser to authenticate. ▎ - If you have an existing Stripe account, log in with your credentials. ▎ - If you’re new, you can create a free Stripe Projects account in seconds. ▎ ▎ Complete the sign-in in your browser, then come back here and let me know when you’re done.
Wait for the user to confirm before proceeding.
Step 6: Hand Off to local stripe-projects-cli skill
Important: After the project is initialized, always use the stripe-projects-cli skill installed at .claude/skills/stripe-projects-cli in the local project directory (invoke via the Skill tool with name stripe-projects-cli) to continue the workflow for adding services. Print out the env variable names returned in a table, but never their values.
Step 7: Provider Recommendations
After a successful ‘add’ output, you must give the user helpful suggestions on other providers services available on Stripe Projects catalog that could be complementary (different primary category) or helpful - 3 to 5 suggestions. NEVER show fabricated commands to provision these services, only ones from the stripe projects catalog output if at all.
Non-Interactive Mode
Always use --json --yes flags to suppress interactive prompts. If a paid service requires confirmation, add --confirm-paid-service.
Working Agreement
- Don’t hand-edit CLI-managed files under
.projectsor the generated.envoutput. - NEVER look at any files in the .projects directory. The CLI manages everything for you.
- NEVER look at the .env file. The CLI manages everything for you.
Error Handling
- Provider not listed at
projects.dev/providers→ stop early, tell the user it’s not supported - Stripe CLI missing → install per platform instructions above
- Plugin missing → install via
stripe plugin install projects projects inittriggers browser login → prompt user, wait for confirmation- Service not in catalog → inform user, suggest
stripe projects catalog --jsonto browse alternatives
Related skills
FAQ
What does stripe-projects do?
stripe-projects provisions services via Stripe Projects CLI.
When should I use stripe-projects?
projects.dev or service API key provisioning request.
Is this skill safe to install?
Review the Security Audits panel on this page before installing in production.