Skip to content
cccskills
FreePublished on GitHubEnglish overview

stripe-projects

Set up services such as databases and SMS for a project through Stripe Projects. Sync generated credentials into `.env`, connect supported provider accounts, and manage credential rotation, plan changes, and service removal.

OriginalShow the original description

Provision SaaS services + sync creds via Stripe Projects.

NousResearch/hermes-agent
Works withStripeVercelPostgreSQL
AI rating100/ 100See how to install

Good for

  • Set up a Postgres database for a project
  • Add an SMS service to an application
  • Sync service credentials and rotate keys
  • Check available providers and change service plans

Overview

What it does

Set up external services for a project through Stripe Projects. This skill checks the supported service catalog, adds services such as Neon Postgres or Twilio SMS, and syncs generated credentials into .env. It records resources in an encrypted vault for each project. You can also review added services, rotate keys, change pricing plans, and remove services. Existing accounts with supported providers can be connected too.

When it helps

Use it when preparing a database or messaging service for application development. It also helps when you want to manage credentials and pricing plans across multiple providers from one place.

Example requests

  • “Provision Neon Postgres for this project.”
  • “Check which services I can add.”
  • “Rotate the keys for the connected services.”

Notes

The skill targets Linux and macOS and requires the Stripe CLI, the Stripe Projects plugin, and a Stripe account. Adding services or changing plans may incur real charges. Because .env is plaintext, keep it out of Git. Check each provider's support before importing existing resources. Removing a service may leave its underlying resource in place.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Objective evaluation

AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.

Clear instructionsIs it clear when to use it and what it does?
AGoodIt identifies use cases for adding services, syncing credentials, rotating keys, and changing plans.
Concrete stepsAre steps, inputs, outputs, and examples spelled out?
AGoodIt specifies commands from init through add and list, along with output to .env and the vault.
SafetyAre sending data, deleting files, and running commands disclosed?
AGoodIt requires surfacing charges before confirmation, checking .gitignore, and checking remaining resources after removal.
Easy setupDoes it need few tools or API keys, and are they documented?
AGoodIt states supported operating systems and Stripe CLI, plugin, and account requirements, with installation guidance.

The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 19, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (1)

  • SKILL.md4.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Stripe Projects Skill

Wraps the Stripe Projects CLI plugin so Hermes can provision SaaS services (Neon, Twilio, Vercel, etc.), generate and sync credentials into the user's .env, and manage billing across providers from one place.

Gated [linux, macos] while the broader payments cluster matures on Windows. The Stripe CLI itself is cross-platform; this gate is a posture for the cluster, not a hard limit.

When to Use

Trigger phrases:

  • "set up <provider>", "provision <Neon|Twilio|Vercel|...>", "create a database"
  • "give me a <Postgres|Redis|Twilio number|...> for this project"
  • "manage my stack credentials", "rotate this key", "upgrade my plan"
  • "what providers can I add?"

If the user already has a provider account, this skill can still connect it with stripe projects link <provider>. If the user wants to use an existing provider resource, such as an existing database or Vercel project, check provider support first; many providers currently support provisioning new resources but not importing existing ones.

Prerequisites

  • Stripe CLI installed (Homebrew on macOS, package manager on Linux, or download from https://docs.stripe.com/stripe-cli/install)
  • Stripe Projects plugin installed
  • A Stripe account. If the user doesn't have one yet, the CLI can guide them through sign-in or account creation in the browser during setup.

Install

macOS:

brew install stripe/stripe-cli/stripe
stripe plugin install projects

Linux: follow the platform-specific install at https://docs.stripe.com/stripe-cli/install, then:

stripe plugin install projects

How to Run

All commands run through the terminal tool from inside the user's project directory (the CLI writes .env and .projects/vault/vault.json into the CWD).

Procedure

1. Initialize the project

cd <project-root>
stripe projects init

This creates .projects/vault/vault.json (encrypted credential store) and prepares the project to receive providers.

2. Discover available providers

stripe projects catalog

Lists every provider Stripe Projects supports — databases, hosting, auth, AI, analytics, messaging, etc.

3. Add a service

stripe projects add <provider>/<service>

Examples:

  • stripe projects add neon/postgres
  • stripe projects add twilio/sms
  • stripe projects add runloop/sandbox

The CLI provisions the service in the user's own account with the provider, generates credentials, syncs them into .env, and records the resource in the vault. The user may need to confirm a tier selection or pricing prompt.

4. Verify

stripe projects list

Should show the newly added provider and its .env keys.

5. Manage / upgrade / remove

stripe projects upgrade <provider>     # tier change
stripe projects remove <provider>      # deprovision
stripe projects rotate <provider>      # rotate credentials

Pitfalls

  • .env writes are real writes. The CLI appends to whatever .env is in the project root. If the user's .env is gitignored (normal), the keys land safely; if not, this skill could be a credential-leak vector. Always check .gitignore first.
  • Per-project state. .projects/vault/vault.json is per-project. Provisioning the same service in two different projects creates two separate resources — and two bills.
  • Billing happens on Stripe's side. Tier prompts during add/upgrade are real charges; surface them to the user before confirming.
  • Provider availability changes. The catalog grows; if a provider the user names isn't listed, stripe projects catalog | grep <name> first instead of failing the add call.
  • Credentials in vault are encrypted but .env is plaintext. Standard .env hygiene applies — never commit it.
  • Removing a service does NOT always destroy the underlying resource. Some providers leave a paused/dormant resource behind. Check the provider's own dashboard after remove for high-cost services (managed databases especially).

Verification

stripe projects --version && stripe projects list

Exit code 0 inside an initialized project means the plugin is healthy.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

1password

FreeSummaryAI rating 100

Set up the 1Password CLI and use stored passwords or API keys in commands and configuration templates. Choose an authentication method, retrieve secret references, and pass credentials to processes through environment variables.

  • Installing and configuring the 1Password CLI
  • Running commands with stored API keys
  • Filling configuration templates with stored secrets
NousResearch/hermes-agent255.2KUpdated Oct 19, 2026

3-statement-model

FreeSummaryAI rating 90

Build an Excel workbook linking the income statement, balance sheet, and cash flow statement. Populate historical figures, create formula-based forecasts, compare scenarios, and check that balances and cash totals agree across all three statements.

  • Populating a financial model template with historical data
  • Building linked forecasts across three financial statements
  • Comparing base, upside, and downside scenarios
NousResearch/hermes-agent255.2KUpdated Oct 19, 2026

accelerate

FreeSummaryAI rating 80

Adapt existing PyTorch training scripts to use multiple GPUs or machines with limited code changes. The skill guides configuration, launch commands, mixed precision, which uses lower-precision numbers, and DeepSpeed or FSDP settings for distributing training work and memory.

  • Move a single-GPU training script to multiple GPUs
  • Configure mixed precision training
  • Set up DeepSpeed or FSDP to reduce memory use
NousResearch/hermes-agent255.2KUpdated Oct 19, 2026

actual-setup

FreeSummaryAI rating 100

Configure Hermes to run AI models through Actual Computer on your own hardware. Set up either the hosted relay or a local connection, select models, verify responses, and troubleshoot request errors or empty output.

  • Connecting Hermes with an Actual inference key
  • Running models through a local Actual daemon
  • Downloading and loading local models
NousResearch/hermes-agent255.2KUpdated Oct 19, 2026

adversarial-ux-test

FreeSummaryAI rating 80

Test an app from the perspective of a frustrated, less technical user. Find confusing steps and barriers, separate actionable usability problems from personal complaints, and produce screenshots, suggested fixes, and prioritized tickets.

  • Reviewing usability before a launch or demo
  • Checking the experience of a new user
  • Finding friction in signup and subscription flows
NousResearch/hermes-agent255.2KUpdated Oct 19, 2026

agent-merge-conflict-arbiter

FreeSummaryAI rating 100

Resolve Git merge conflicts between two agents by comparing both changes and their stated goals. Combine compatible work, explain choices where designs differ, and verify the merged result with project builds or tests.

  • Resolving conflicts between branches edited by two agents
  • Integrating changes from parallel worktrees
  • Reviewing reasons for conflicting design choices
NousResearch/hermes-agent255.2KUpdated Oct 19, 2026

See all skills by NousResearch

Report a problem with this skill