Sc convex cloud
Convex Cloud (managed) deploy operations. Run 'npx convex deploy' against a Cloud deployment using CONVEX_DEPLOY_KEY, output the injected NEXT_PUBLIC_CONVEX_URL, and probe the deployment (/version on *.convex.cloud + JWKS on *.convex.site). The online-path counterpart to /sc-convex (self-hosted on Dokploy).From its SKILL.md
npx -y skills add rahmanef63/si-coder-agent --skill sc-convex-cloudAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
4 things to look at
- reads credentialsReads from 1 credential source: `CONVEX_DEPLOY_KEY`.
- 13 stars13 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- runs commandsInstructs the agent to run 4 commands, including `node scripts/deploy-cloud.js` and 3 more.
- fetches URLsInstructs the agent to fetch 2 URLs, including https://<name>.convex.cloud/version and 1 more.
SKILL.md
5.3 KB, ~1.4k tokens by cl100k_base, as published. Nobody here has run it
/sc-convex-cloud — Convex Cloud (managed)
Use this skill when the user wants to deploy, debug, or maintain a Convex Cloud (managed) backend — the online-path counterpart to /sc-convex (self-hosted on Dokploy). The repo lives at https://github.com/rahmanef63/si-coder-agent.
flowchart LR
A["/sc-convex-cloud"] --> B["scripts/deploy-cloud.js<br/>CONVEX_DEPLOY_KEY (env, never echoed)"]
B --> C["npx convex deploy<br/>→ Convex Cloud"]
C --> D["inject NEXT_PUBLIC_CONVEX_URL<br/>into the build"]
D --> E["probe /version (*.convex.cloud)<br/>+ JWKS (*.convex.site)"]
E --> F["ready ✅"]
NEVER ask the user to run Convex CLI by hand
All Convex Cloud deploys go through scripts/deploy-cloud.js. Do not instruct the user to run npx convex deploy interactively, nor to hand-set NEXT_PUBLIC_CONVEX_URL. The deploy key is passed via the script's env and never echoed. If a deploy fails, debug it with scripts/check-cloud.js and fix root cause — do not punt the Convex CLI call to the user.
Pre-requisites
CONVEX_DEPLOY_KEY— production (or preview) deploy key for the Cloud deployment. Required.CONVEX_DEPLOYMENT— optional local-dev marker written bynpx convex dev. NOT used in CI.
If CONVEX_DEPLOY_KEY is missing, route the user to /sc-onboarding.
CORE MANDATES (LEARNED LESSONS)
- Coupled build is the source of truth for the URL: let
npx convex deploy --cmd '<build>'injectNEXT_PUBLIC_CONVEX_URLat build time. Never hardcode the URL in two places — the--cmdinjection wins. - Next.js needs the
NEXT_PUBLIC_prefix override: the default injected var isCONVEX_URL, which never reaches the browser. ALWAYS pass--cmd-url-env-var-name NEXT_PUBLIC_CONVEX_URL. - Deploy key is a secret: never log/echo it. Pass it via the process
env, never interpolate it into a shell command string. - Set
CONVEX_DEPLOY_KEYonly on the matching env: a prod key → Production only; a preview key → Preview only. Never setCONVEX_DEPLOYMENTin CI. - Project + key creation is human-one-time: there is no anonymous Cloud-project create API. Mint keys headlessly only after a first interactive login (
npx convex deployment token create <name> --prod --save-env).
Required env vars
| Variable | Format | Purpose |
|---|---|---|
CONVEX_DEPLOY_KEY | prod:<name>|eyJ2… or preview:… | Authenticates npx convex deploy against the Cloud deployment (SECRET) |
CONVEX_DEPLOYMENT | prod:<name> / deployment name | Optional local-dev marker only; leave blank in CI |
Scripts
All scripts live in skills/sc-convex-cloud/scripts/ (repo-relative; the usage blocks below assume this cwd). On install, this skill is symlinked into ~/.claude/skills/sc-convex-cloud/, so the same paths resolve there too.
deploy-cloud.js
Run a Convex Cloud deploy. Coupled build (default) runs the frontend build via --cmd and injects NEXT_PUBLIC_CONVEX_URL; --backend-only pushes just the backend (when Vercel runs the coupled build itself). Prints NEXT_PUBLIC_CONVEX_URL=<url> — never the deploy key.
node scripts/deploy-cloud.js \
[--build-cmd 'npm run build'] \
[--url-env NEXT_PUBLIC_CONVEX_URL] \
[--backend-only] \
[--message "deploy message"] \
[--cwd <path>]
check-cloud.js
Probe a Cloud deployment's /version (on the *.convex.cloud host) + /.well-known/jwks.json (on the *.convex.site host — that's where @convex-dev/auth serves JWKS). Derives the URL from CONVEX_DEPLOY_KEY when --url is omitted. Prints a status table. /version is required; JWKS is advisory (a deployment without @convex-dev/auth has none) and only gates the exit code when you pass --expect-auth. Exits 2 if a required probe is not ok.
node scripts/check-cloud.js --url https://<name>.convex.cloud
# require JWKS too (the deployment is expected to run @convex-dev/auth):
node scripts/check-cloud.js --url https://<name>.convex.cloud --expect-auth
# or, deriving from the prod deploy key:
node scripts/check-cloud.js
Diagnosis
| Symptom | Cause | Fix |
|---|---|---|
| Client connects to wrong backend | NEXT_PUBLIC_CONVEX_URL not injected | Ensure --cmd-url-env-var-name NEXT_PUBLIC_CONVEX_URL is set on the coupled build |
Browser shows CONVEX_URL unset | Missing NEXT_PUBLIC_ prefix override | Pass --url-env NEXT_PUBLIC_CONVEX_URL (default) — never the bare CONVEX_URL |
JWKS (*.convex.site) not 200 | @convex-dev/auth keys not configured on the deployment (or a probe pointed at the wrong host) | JWKS is served on *.convex.site, NOT *.convex.cloud; configure @convex-dev/auth keys on the deployment via the dashboard / env. Advisory unless check-cloud.js --expect-auth |
deploy-cloud.js exits 1 immediately | CONVEX_DEPLOY_KEY missing | Set it (route to /sc-onboarding) — never run the CLI by hand |
check-cloud.js cannot derive URL | preview key (branch-derived name not in key) | Pass --url https://<name>.convex.cloud explicitly |
What ships with it: 2 files
4.7 KB alongside SKILL.md, 2 of them executable
scripts/
- check-cloud.jsruns2.4 KB
- deploy-cloud.jsruns2.3 KB