Agent skill · software engineering · aiskillstore
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 this skill is useful
Adds executable scripts for provisioning third-party services and managing credentials through the Stripe Projects CLI, which the AI wouldn't generate on its own.
What it needs
Requires stripe installed locally. Requires stripe account access. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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: 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: Step 2: Search the Catalog Confirm the requested provider/service exists: If resultcount 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: Step 3: Initialize a Project Check if a project is already initialized: If not initialized: (don’t use ‘–json’ for this command) If the CLI output indicates a browser was opened for authentication, stop and clearly tell the user to complete sign-in in their browser. Don’t run further commands until they confirm they’re done. 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: If MISSING: re-run stripe projects init --yes — the skill is bundled with the Projects plugin and installed during init. If OK: use the locally-installed stripe-projects-cli skill (invoke using the Skill tool with name stripe-projects-cli) to continue the workflow — adding services, managing credentials, and configuring the project. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/stripe-projects