What problem does it solve? Keeping Stripe products and prices in sync with a bundle catalogue is error-prone when done by hand, especially across test and live modes. This Skill runs the repository's stripe-setup script safely: dry run first, test mode on approval, live mode on a separate explicit approval, then lands the resulting price ids in the environment files. ## Core Features & Use Cases - Dry-run planning: Lists which Stripe products and prices already exist and which would be created, writing nothing, so the operator can review the plan first. - Staged test and live sync: Runs the sync in Stripe test mode on one approval, then requires a separate explicit approval before touching live mode. - Price id landing: Writes the printed STRIPE_PRICE_ID_* and STRIPE_TEST_PRICE_ID_* values into .env.ci and .env.prod and opens a PR with only those changes. - Use Case: A bundle's subscription price changes in web/public/submit.catalogue.toml. Invoke this Skill to dry-run the change, create the new price in test and live Stripe, and commit the new price ids without ever exposing secret keys. ## Quick Start Ask the assistant to sync the Stripe catalogue for the bundle whose price just changed, starting with a dry run in test mode.