convex/agent-skills

convex-optimize

Audit and optimize an existing Convex app: security, scale, upgrades, observability.

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/convex/agent-skills --skill convex-optimize

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

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

Audit and optimize an existing Convex app

The remediation WORKFLOW for an existing app: open with a scored assessment, then act on it — upgrade stale components and set up observability — plan-then-confirm-then-apply. The assessment itself is delegated to launch-readiness (the findings-bus scorer); optimize's distinct value is the actions it takes on the result.

Workflow

  1. Detect the app: a convex/ directory, the schema, and whether it's an anonymous or cloud deployment.
  2. ASSESS via launch-readiness — one scored, deduped report across authz/reviewer/advisor/insights with an ordered fix plan. Do not re-run those passes by hand; optimize consumes launch-readiness's report rather than re-implementing the audit.
  3. UPGRADE: run check-updates against the pinned @convex-dev/* components and fold stale-component (staleness-class) findings into the same plan.
  4. OBSERVABILITY: if the readiness report flagged an observability gap (no prod error capture), offer to install sentinel.
  5. Present the combined prioritized plan — the launch-readiness score + the fix plan + upgrades + observability, security/data-loss first — and apply only on explicit confirmation, dispatching each fix to its fixCapability.
  6. After applying, re-run the launch-readiness assessment and show the score delta.

Rules

  • Read-only first. Present a plan and CONFIRM before changing any file.
  • Delegate the audit to launch-readiness (the findings-bus scorer); don't re-implement reviewer/advisor/insights inline — optimize's job is acting on the report (upgrades + observability), not re-scoring.
  • Prioritize security and data-loss risks above style, following launch-readiness's ordering.
  • Never auto-land changes on someone's existing prod app; re-assess after applying and show the score moved.

Relacionados por tarefa

do mesmo repositório

Mais Skills

Todos os Skills
convex
Comunidade

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.

Instalações totais
140,8 mil
GitHub Stars
70
Atualizado
20 de nov.
convex
Comunidade

convex-quickstart

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

Instalações totais
141 mil
GitHub Stars
70
Atualizado
20 de nov.
convex
Comunidade

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,

Instalações totais
118,1 mil
GitHub Stars
70
Atualizado
20 de nov.
convex
Comunidade

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.

Instalações / 1h
9
GitHub Stars
70
Atualizado
20 de nov.