What problem does it solve?
Convex projects span multiple deployments (local, dev, preview, prod), and commands aimed at the wrong target cause silent failures or accidental production changes. This Skill enforces a discipline of identifying and announcing the deployment target before any deployment-affecting command runs.
Core Features & Use Cases
- Target Classification: Reads CONVEX_DEPLOYMENT, convex.json, and CONVEX_DEPLOY_KEY (or the Convex MCP status tool) to classify the target as local-anonymous, dev, preview, or prod.
- Prod Consent Gating: Requires a fresh, explicit, per-session confirmation before prod deploys, prod env changes, snapshot import/export, or prod-scoped MCP sessions.
- MCP Safety Defaults: Starts the Convex MCP scoped to non-prod and keeps the read-only prod flag separate from the mutating prod flag.
- Read-Only Session Mode: Honors user-requested read-only mode absolutely, disabling deploys, env mutations, and imports for the session.
- Use Case: Before running
npx convex deploy, the agent announces target: dev (joyful-capybara-123, personal dev) and only proceeds after confirming the correct deployment.
Quick Start
Ask the agent to check which Convex deployment my project currently targets before running any deploy command.