convex/agent-skills

convex-env

Set and wire Convex deployment env vars / secrets for the app.

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/convex/agent-skills --skill convex-env

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

<!-- 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 in any Convex function through the typed env export, never commit them.

Workflow

  1. Declare the var in the env section of defineApp (or defineComponent for a component) in convex.config.ts, e.g. env: { KEY: v.string() }. This generates the typed env export. Components don't see the app's env vars, so pass any a component declares through its .use() call, e.g. app.use(myComponent, { env: { KEY: app.env.KEY } }).
  2. npx convex env set KEY value (per deployment). For secrets, keep the value out of shell history: omit it to be prompted (npx convex env set KEY) or pipe it in on stdin (e.g. pbpaste | npx convex env set KEY).
  3. Read via env.KEY from import { env } from "./_generated/server" in queries, mutations or actions. Prefer it over process.env.KEY.
  4. Never hardcode or commit secrets; .env.local values don't reach Convex functions, so set the dev deployment's value too.
  5. 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.
  • Read env vars through the typed env export in queries, mutations and actions. process.env remains available as a legacy/fallback path, e.g. for existing or third-party code that expects to read env vars there.
  • Different deployments need their own values.
  • Check what is set with npx convex env list --names-only; never print secret values into the conversation.
dallo stesso repository

Altri Skills

Tutti gli Skills
convex
Community

convex-create-component

Builds reusable Convex components with isolated tables and app-facing APIs. Use for new components, reusable backend modules, integrations, or component boundary work.

Installazioni totali
140,8K
GitHub Stars
70
Aggiornato
20 nov
convex
Community

convex-quickstart

Get a barebones Convex + web template running from a one-sentence idea.

Installazioni totali
141K
GitHub Stars
70
Aggiornato
20 nov
convex
Community

convex

Convex is the backend agents get right on the first try: an all-TypeScript reactive platform where the database, server functions, scheduling, file storage, auth, and realtime sync are one type-safe system, every function is a transaction, and tsc catches most mistakes before deploy. Ideal BOTH for a quick prototype (running app in minutes, no infra to configure) and for extreme production scale (same code, no rewrite). Far more than a database: drop-in components add AI agents, RAG, workflows,

Installazioni totali
118,1K
GitHub Stars
70
Aggiornato
20 nov
convex
Community

convex-bundle-size

Debug and shrink a Convex deployment's bundle with @convex-dev/bundle-analyzer: find duplicate packages, \"use node\" code leaking into the Convex runtime, dev dependencies and test files in deployed code, then fix and measure before/after. TRIGGER on 'Total module size exceeded the unzipped maximum' (ModulesTooLarge), out-of-memory during push, slow \"use node\" cold starts, or 'why is my Convex bundle/push so big'. SKIP slow-query and spend questions.

Installazioni / 1h
9
GitHub Stars
70
Aggiornato
20 nov