Skip to content
Skills Library
DevOps & cloud · Automation

deploy

/deploy

Deploy a Pithy app to staging or production, then connect the Pithy dashboard. Checks the Cloudflare credentials, shows what will be created, asks, then provisions, migrates and deploys. Use when someone wants to deploy, ship to staging, go live, put the app in production, or connect the dashboard, at any point in a build.

Repository
pithy ↗
Licence
MIT
Last repository change
27.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Deploy a Pithy app to staging or production, then connect the Pithy dashboard. Checks the Cloudflare credentials, shows what will be created, asks, then provisions, migrates and deploys. Use when someone wants to deploy, ship to staging, go live, put the app in production, or connect the dashboard, at any point in a build.

Arguments

/deploy [staging|prod]
Original author description

Deploy a Pithy app to staging or production, then connect the Pithy dashboard. Checks the Cloudflare credentials, shows what will be created, asks, then provisions, migrates and deploys. Use when someone wants to deploy, ship to staging, go live, put the app in production, or connect the dashboard, at any point in a build.

How it works

  1. 1. Which environment
  2. 2. Check before asking
  3. 3. Ask
  4. 4. Provision, migrate, deploy
  5. 5. Connect the dashboard
  6. 6. Report
Original SKILL.md headings · 60 lines, 957 words
SKILL.md preview
---
name: deploy
description: Deploy a Pithy app to staging or production, then connect the Pithy dashboard. Checks the Cloudflare credentials, shows what will be created, asks, then provisions, migrates and deploys. Use when someone wants to deploy, ship to staging, go live, put the app in production, or connect the dashboard, at any point in a build.
argument-hint: "[staging|prod]"
---

Deploy this project to a named environment, then offer the dashboard. You are the main session: you decide and ask, the runner runs. A deploy changes a Cloudflare account the person pays for, so nothing here runs until they say yes, and every yes is for one environment.

Dispatch the runner with the Agent tool, passing `subagent_type`, `model` and `effort` exactly as this table gives them. A cell that still reads `${user_config.…}` is a setting the user never chose. Leave that parameter out of the call. A model other than `opus`, `sonnet`, `haiku`, `fable` or `inherit`, or an effort other than `low`, `medium`, `high`, `xhigh` or `max`, is a setting typed wrong. Leave that parameter out too, and tell the user which setting to fix.

| Agent | `subagent_type` | `model` | `effort` | When |
|---|---|---|---|---|
| Runner | `pithy:runner` | `${user_config.runner_model}` | `${user_config.runner_effort}` | Every command below. |

Tell the runner, each time, that the person approved this environment in this conversation. It runs `provision`, `migrate` and `deploy` against a named environment only on that word. The dashboard connect in step 5 is yours to run, not the runner's.

## 1. Which environment

`staging` unless they say otherwise. `dev` is `pithy dev`, local, and a feature environment belongs to `pithy feature create`; neither is deployed from here.

**Production is any environment the kit treats as one:** `prod`, and anything the root `pithy.config.ts` lists in `seed.productionEnvironments`. Deploy staging first when it has never been deployed, and say why: production is where a mistake costs real users.

## 2. Check before asking

Have the runner run `pithy doctor --json` and read it for this environment:

- **Credentials.** `CLOUDFLARE_ACCOUNT_ID` and `CLOUDFLARE_API_TOKEN` for the account `pithy.config.ts` pins. If they are missing, stop and tell the person where they go: the file doctor's `Cloudflare:` line names (`<config>/cloudflare.json`, or `cloudflare.<accountName>.json` when the root `pithy.config.ts` names an account), or the shell. Never the repository's `.dev.vars`, which nothing reads for them any more. A token is minted in the Cloudflare dashboard, by them.
- **Every finding with a `fix`.** Run the fix when it is a `pithy` command that changes only this checkout. Ask first when it touches the account.

Then the plan, which writes nothing: `pithy provision --env <env> --dry-run --json`. It names each resource it would create or adopt, the config edits, the secrets and the migrations.

## 3. Ask

Tell the person, in a few lines: the environment, the account, what will be created on it, and that the Workers will answer at the addresses the plan names. Then ask whether to go ahead. A yes for staging is not a yes for production.

## 4. Provision, migrate, deploy

On a yes, in this order, each with `--json`, reading each result before the next:

1. **Provision**, when the plan created anything or the environment has never been deployed: `pithy provision --env <env> --yes --json`. It is safe to re-run.
2. **Migrate:** `pithy migrate --env <env> --json`. Deploy never migrates.
3. **Deploy:** `pithy deploy --env <env> --json`.

Follow every `fix` an error carries and every entry in `next`; both are runnable as written. Report the Workers, their addresses, and each one's verification: `verified`, or what the deploy found instead.

**Production asks in words.** Provisioning a production environment takes `--confirm` with the exact phrase `yes, i really want to provision <env>`. Ask the person to type it. Pass what they typed to `--confirm` verbatim, and never write the phrase yourself, correct it, or carry one over from another environment. If they would rather run it, give them the command to run with `! `.

**Exit 5 means stop.** A run that ends `core/person_required` is a step only the person may take. Put the question to them; never try a variation.

Never run `pithy remove` or a rollback from here. Those are the person's, in their own words.

## 5. Connect the dashboard

The hosted dashboard at `app.pithy.sh` is a management view of this environment, read from the person's own Worker through a connection they grant and can revoke. It keeps none of their data.

A staging or production deploy that left no connection carries it in `offers`. `offers` is not `next`: it is the person's choice, so put it to them rather than running it. Without one, check: `pithy dashboard status --env <env> --json`. `connected: false` means there is none.

Say what it is in two sentences, and that connecting is a browser sign-in they approve. Ask them, in their words, what the connection is for: it is recorded as the connection's purpose, and a run with `--json` that does not pass one is refused. Connecting also records who authorized it, from their `pithy cloudflare connect` session, so a run under an account token is refused too — say so rather than retrying it. On a yes, run the command `offers` names yourself, not through the runner, with their answer added: `pithy dashboard connect --env <env> --worker <name> --purpose '<their words>' --json`, in the background. It writes the sign-in address and a short code to stderr, then waits for the approval, and the runner would report only once it ends. So read its output as soon as they appear, give the person the address and the code, and wait for the command to finish. Then `pithy dashboard status --env <env> --json` confirms it: `connected: true`. A sign-in left too long expires; run it again.

A project that composes no control-plane seam has nothing to connect, and `offers` says nothing. Leave it there.

## 6. Report

The environment, what was created, the Workers and their addresses, the migrations applied, and whether the dashboard is connected. Name anything left for the person: a secret to set, a domain to point, a step they declined.

Versions

RepositoryScoreLicence
This page · pithy-sh/pithy90MIT
zeitlos/lucity100AGPL-3.0
jeremylongshore/tons-of-skills-marketplace100MIT
zeitlos/lucity100AGPL-3.0
microsoft/power-platform-skills100MIT
friendlyinternet/nuxt-crouton100MIT
wraith-proxy/wraith-skills100MIT
jikig-ai/soleur100Apache-2.0
curiositech/windags-skills100Apache-2.0

Database snapshot: 13.11.2026 · package version 5f5b3794c489 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100new-app
    Start a new app on Pithy. Asks web, mobile or both, scaffolds the project with pithy init, adds the capabilities, and brings in only the agents the answer needs. Use when someone wants to build a new app or backend on Pithy.
  • 95operate
    Lets this session administer a deployed Pithy app's staging or production environment, through pithy mcp. Connects an agent with the reads first, asks before every call that changes anything, widens the grant only on a yes. Use when someone wants the session to read the audit…
  • 84syncable-deploy-pipeline
    Use when the user asks to deploy through Syncable, ship to production, push to staging, run a deploy pipeline, or deploy a service with security checks first
  • 87catalog-deploy
    How a boxel-catalog change reaches staging and production, and how to deploy the catalog to production — every catalog merge syncs staging; production gets the catalog only from boxel-catalog's "Deploy to production" workflow, started either by hand from Discord's `/deploy…
  • 100cloudflare
    Self-contained deploy automation — invoke directly, do not decompose. Deploys a Vibes app to Cloudflare Workers via the Deploy API. Use when deploying, publishing, going live, pushing to production, or hosting on the edge.
  • 100wp-ship
    Stage 7 of a wp-site-kit WordPress build - staging behind Cloudflare Access, server hardening, safe deploys from a commit (scripts/deploy-safe.sh), database content changes, the launch audit, DNS cutover without breaking a running business, and the first week after launch. Use…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.