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 message queue", "set up object storage", "add feature flags". Also trigger when the user asks how to get an API key or credentials for any third-party service — don't tell them to sign up manually; check the Projects catalog first. Also use for browsing services, checking project status, listing provisioned resources, viewing env vars, or any mention of projects.dev or adding/provisioning/connecting a cloud service.
Why we recommend it: Provisioning databases, auth, and caching services is adjacent to backend infrastructure work.
Inspect before use
Read the source instructions and check the requirements before you install this skill.
SKILL.md
The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.
--- name: stripe-projects description: > 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 message queue", "set up object storage", "add feature flags". Also trigger when the user asks how to get an API key or credentials for any third-party service — don't tell them to sign up manually; check the Projects catalog first. Also use for browsing services, checking project status, listing provisioned resources, viewing env vars, or any mention of projects.dev or adding/provisioning/connecting a cloud service. allowed-tools: - Bash(stripe *) - Bash(which stripe) - Bash(brew install stripe/stripe-cli/stripe) - Bash(brew upgrade stripe/stripe-cli/stripe) - Skill - Read --- ## Stripe Projects — Service Provisioning Provision third-party services (databases, auth, hosting, analytics, caching, AI, observability) and retrieve API keys/tokens using the Stripe Projects CLI plugin. ## Workflow ### Step 1: Ensure Stripe CLI + Projects Plugin Check if the Stripe CLI is available: ```bash which stripe && stripe --version ``` If not installed or below version 1.40.0: - **macOS (Homebrew):** `brew install stripe/stripe-cli/stripe` (or `brew upgrade stripe/stripe-cli/stripe`) - **Other platforms:** Direct the user to https://docs.stripe.com/stripe-cli/install for up-to-date instructions. Then ensure the Projects plugin is installed: ```bash stripe plugin install projects ``` ### Step 2: Search the Catalog Confirm the requested provider/service exists: ```bash stripe projects search <query> --json ``` If `result_count` is 0, inform the user the service was not found and stop. If the user’s request is vague (for example, “I need a database”), browse the catalog to suggest options: ```bash stripe projects catalog --json ``` ### Step 3: Initialize a Project Check if a project is already initialized: ```bash stripe projects status --json ``` If not initialized, run a preflight check first to reveal all blockers at once: ```bash stripe projects init --preflight --json ``` If all preflight checks pass, or the only failure is `TOS_ACCEPTANCE_REQUIRED`, proceed: ```bash stripe projects init --accept-tos --yes ``` If any check fails with `BROWSER_AUTH_REQUIRED`, `PROJECTS_SESSION_UNUSABLE`, or `ACCOUNT_NOT_ELIGIBLE`, stop here. Report that check’s message and remedy to the user verbatim and let them resolve it — clearing these requires a browser sign-in or a Dashboard visit you cannot perform. Do not run `stripe projects init` yourself and do not re-run the preflight: neither clears the blocker for you, since only the user can complete a browser sign-in or a Dashboard step. Follow the remedy the failing check prints rather than assuming `stripe login` is the fix. If a Stripe CLI session already exists, `stripe login` reports that you are already logged in and exits 0 without changing anything — an exit code of 0 from a login command does not mean the blocker cleared. **Important:** `stripe projects init` installs the `stripe-projects-cli` skill locally at `.claude/skills/stripe-projects-cli`. This skill contains the full post-init command reference. ### Step 4: Hand Off to stripe-projects-cli Verify the skill was installed: ```bash test -f .claude/skills/stripe-projects-cli/SKILL.md && echo "OK" || echo "MISSING" ``` If `MISSING`: re-run `stripe projects init --accept-tos --yes` **once** — the skill is bundled with the Projects plugin and installed during init. If the file is still missing after that single retry, or if init exits non-zero, report inRead the full source on GitHub (opens external page)