sc-convex-cloud

# /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`. ```mermaid 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 ✅"] ``` ## Connection-safe local execution For a direct Convex Cloud `source=sc` named connection, execute credential-dependent helpers through `sc run -- ...`, for example: ```bash sc run -- node skills/sc-convex-cloud/scripts/deploy-cloud.js --help ``` The plain `node scripts/...` examples below describe the script interface. Do not export `CONVEX_DEPLOY_KEY` globally merely to satisfy them. Composio-backed connections execute through Composio rather than `sc run`. ## NEVER ask the user to run Convex CLI by hand Prefer an existing project-owned release wrapper because it owns environment isolation, custom domains and verification. Otherwise use `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 f...