Skip to content

Convex env vars and secrets

Set, read and verify Convex deployment environment variables and secrets safely

Stars
9,546
Licence
MIT
Files
1 file

What it does

When installed, the agent knows how to store API keys and other secrets in the Convex backend's environment variables rather than in source code. It guides setting them per deployment with the Convex command-line tool, reading them inside server actions, and checking they were saved. It also reminds the agent never to commit secrets to git.

Great for

  • Developers building apps on the Convex backend platform who need to add API keys
  • Teams wanting a consistent, safer way to handle secrets across dev and production deployments

Skip it if

  • People who do not use Convex (the commands and rules are specific to it)
  • Anyone expecting a full secrets manager; this only covers Convex environment variables and gives no protection if secrets are pasted into chat or logs

Try asking

  • “Add my Stripe secret key to the Convex production deployment”
  • “Wire the OpenAI API key so my Convex action can read it”
  • “Check which environment variables are currently set in my Convex project”
Step-by-step guide: how to use Convex env vars and secretsInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 1 original files, the MIT licence and an attribution note.

    convex-env.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip convex-env.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip convex-env.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Tell the agent which deployment (dev or prod) you mean, since each needs its own values
  • Paste secret values into your terminal yourself rather than into chat, so they are not stored in conversation history
  • Review any command the agent runs that touches env vars before approving it

What's inside

  • SKILL.md

Redistributed unmodified from openclaw/clawhub under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.