Skip to main content
affpapa.org
RU EN
skill CX Codex

convex-env — Claude Code skill: what it does, how to install

This skill sets and wires Convex deployment environment variables and secrets. Use it when actions need deployment-specific values without putting secrets in code.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add convex/agent-skills --skill convex-env -a claude-code
Open on GitHub

What convex-env does

convex-env shows how to store secrets as Convex deployment environment variables with npx convex env set KEY value, then read them through process.env.KEY inside actions. An action may need 'use node'. Queries and mutations are outside this workflow.

Secrets stay out of source code and Git. For local work, values can go in .env.local; each deployment needs its own values. To inspect configured names without exposing secret values, run npx convex env list --names-only. Check every deployment before running the app, because a variable name can exist in one deployment and still need a separate value in another.

What it helps with

  • set a secret for a Convex deployment
  • read an environment variable inside an action
  • keep values separate across deployments
  • check configured secret names without printing values
  • keep credentials out of code and Git

Example prompts for the agent

  • Set up the Convex secrets for this deployment and show how to verify the variable names without revealing values.
  • Inspect the project for process.env usage and move any reads from queries or mutations into actions.
  • Use .env.local for local values and set the deployment secret with npx convex env set KEY value.

How to install convex-env

1Skills CLI (Vercel)

npx skills add convex/agent-skills --skill convex-env -a claude-code

2Manually: put the files in place

~/.claude/skills/convex-env/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/convex-env/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

From the same set32

convex-docs Pins the project's installed Convex version and fetches current markdown docs or checks types instead of generating outdated API calls. CX Codex +1 36,100installs convex-add Adds hosting or another backend capability to the current Convex app. Use it when you want an agent to locate and wire a requested component. CX Codex +1 35,900installs convex-advisor Reads a Convex deployment's 72h insights, root-causes each event in code, and reports fixes ranked by severity. CX Codex +1 35,900installs convex-crons Adds recurring scheduled jobs to Convex applications. Useful when you need to schedule backend maintenance and periodic cleanups. CX Codex +1 36,000installs convex-seed Populates Convex database tables with sample rows or imports external datasets. Useful when preparing dev environments without manual data entry. CX Codex +1 35,800installs convex-verify convex-verify tests a Convex feature with seeded data, multiple mocked identities, and negative authorization checks. Use it for a specific feature you have built or changed. CX Codex +1 35,800installs convex-monitor This skill blocks on the next event in a Convex app — a dev error, a prod error or a feature request — and hands it to the agent. CX Codex +1 35,800installs convex-billing Adds Stripe payments and subscriptions to a Convex app using @convex-dev/stripe with checkout sessions, webhooks, and subscription gating. CX Codex +1 35,800installs

Similar

convex-security-check waynesutton Checks a Convex backend before merge for exposed functions, missing auth, weak validation, ownership gaps, and secrets in code. CX Codex +1 2,700installs convex-security-audit waynesutton A skill that walks through a Convex app's security and writes up what it finds. Useful before a launch or after an incident. CX Codex +1 1,500installs convex Mindrally Tells the agent how to write Convex code: queries, mutations, actions, indexes and file uploads. Useful once Convex is your backend. CX Codex +1 651installs env-vars official Vercel Labs Learn how the skill handles Vercel environment variables, .env files, CLI commands, and local OIDC tokens. Useful when setting up a project or tracing auth errors. CX Codex GP ChatGPT 7installs python-configuration Seth Hobson This skill moves Python settings into environment variables and validates typed configuration. Use it for secrets and environment-specific behavior. CX Codex 11,508installs env-secrets-manager Alireza Rezvani This skill audits environment variables and scans repositories for likely secret leaks. Use it before config changes, during rotation planning, or in incident triage. 667installs

Nearby in Backend and APIs

Everything for Backend and APIs →

Questions about convex-env

How do I install convex-env in Claude Code?

Run npx skills add convex/agent-skills --skill convex-env -a claude-code, then run npx skills add convex/agent-skills --skill convex-env -a claude-code again. The skill file is at ~/.claude/skills/convex-env/SKILL.md.

What does convex-env do?

It sets Convex deployment environment variables and secrets, explains how to read them with process.env.KEY in actions, and checks configured names without printing secret values.

Where can convex-env read environment variables?

The workflow uses process.env inside actions. It should not be used in queries or mutations, and an action may require 'use node'.

Source text

SKILL.md · Apache-2.0 
---
name: convex-env
description: "Set and wire Convex deployment env vars / secrets for the app."
---

<!-- GENERATED from convex-agents content/capabilities/env.json — do not edit by hand. -->

# Manage env vars + secrets

Store secrets as Convex deployment env vars (npx convex env set), read them with process.env in actions, never commit them.

## Workflow

1. `npx convex env set KEY value` (per deployment).
2. Read via process.env.KEY inside actions (not queries/mutations).
3. Never hardcode or commit secrets; add to .env.local only for local.
4. Confirm it's set with `npx convex env list --names-only`, which lists names without printing the secret values.

## Rules

- Secrets live in Convex env vars, never in code or git.
- process.env only in actions ('use node' if needed), not queries/mutations.
- Different deployments need their own values.
- Check what is set with `npx convex env list --names-only`; never print secret values into the conversation.

© convex · Apache-2.0 · convex/agent-skills

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor