stripe-projects
Use when the user wants to provision infrastructure or third-party services using Stripe Projects. Triggers: "I need a database", "set up auth", "add caching", "give me a Postgres", "provision Redis", "I need hosting", "add a vector DB", "get me an API key for X", "get credentials for X", "sign up for a service", "set up monitoring", "show me the catalog", "what can I provision", "browse providers", "add an LLM provider", "configure model provider", "add email sending", "set up search", "add a m
Security Assessment
Detected risks:
About stripe-projects
The stripe-projects skill provisions third-party services (databases, auth, hosting, caching, AI providers, observability, and more) and retrieves their API keys using the Stripe Projects CLI plugin. It triggers whenever a user needs to set up infrastructure or get credentials for a service, steering them to the Projects catalog instead of manual signup.
Its workflow ensures the Stripe CLI and Projects plugin are installed, searches the catalog to confirm a provider exists (browsing it for vague requests), initializes a project (pausing for browser sign-in when required), and hands off to a locally installed stripe-projects-cli skill for adding services and managing credentials. The CLI is the source of truth, managing state under .projects/ and generating .env files that should not be hand-edited. The skill reports provisioned services with environment variable names only, never their values, and never fabricates provider names or commands.
It is most useful for developers who want to provision backing services and obtain credentials quickly from a managed catalog, with safe handling of secrets and project state.
FAQ
When should I use this skill?
When you want to provision a third-party service (database, auth, hosting, caching, AI, observability, and others) or get an API key or credentials for one.
How does it work?
It ensures the Stripe CLI and Projects plugin are installed, searches the catalog, initializes a project, and hands off to the local stripe-projects-cli skill to add services and manage credentials.
How does it handle secrets?
It reports environment variable names only and never their values, and treats the CLI as the source of truth, leaving generated .env and .projects state un-edited.
What if a requested service is not found?
It informs the user the service was not found and stops, suggesting the catalog command to browse alternatives, and never fabricates provider names or commands.
Install stripe-projects
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
stripe/ai