mcpField
C
convex-optimize

convex-optimize

github.com/convexDevelopment6937.1k installsUpdated 1d ago
Repository

About convex-optimize

convex-optimize is a skill for auditing and improving an existing Convex app. It combines launch-readiness findings with component updates and observability actions, and requires confirmation before making changes.

Key features

  1. 01Detects Convex app and deployment type
  2. 02Uses launch-readiness assessment
  3. 03Checks pinned component updates
  4. 04Offers sentinel for observability gaps
  5. 05Confirms plan before applying fixes
  6. 06Reassesses and reports score change

Use cases

  1. 01Prioritizing security and data-loss fixes
  2. 02Updating stale Convex components
  3. 03Adding production error capture
  4. 04Reviewing assessment changes after remediation

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/convex/agent-skills --skill convex-optimize

After installing, type/convex-optimizein Claude Code to confirm it loaded.

Details

From the project README

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.

Comments

Markdown supported