---
id: gh-convex-optimize
name: "convex-optimize"
url: https://skills.yangsir.net/skill/gh-convex-optimize
author: convex
domain: ai-system-observability-sre
tags: ["convex", "audit", "observability", "security", "performance"]
install_count: 35000
rating: 4.60 (120 reviews)
github: https://github.com/convex/agent-skills/tree/main/skills/convex-optimize
---

# convex-optimize

> 此技能对已有的 Convex 应用做一次带评分的全面体检（安全、扩展性、组件版本、可观测性），并据此自动升级过时组件、补齐线上错误监控。它把安全与数据丢失风险排在最前，先出方案再确认执行，最后复评展示分数变化，适合上线前或长期维护阶段使用。

**Stats**: 35,000 installs · 4.6/5 (120 reviews)

## Before / After 对比

### 上线前的全面体检与修复

**Before**:

上线前要手工翻查鉴权、代码评审、顾问建议和运行时洞察四类问题，重复跑同一批检查，还得自己记住哪些组件版本过期、线上有没有错误捕获，常常漏项。

**After**:

此技能一次产出带评分且去重的诊断报告，把安全与数据丢失风险排在最前，自动折叠过时组件与监控缺口，确认后逐项修复并复评展示分数变化。

| Metric | Before | After | Change |
|---|---|---|---|
| 完成一轮审计耗时 | 240分钟 | 25分钟 | -90% |
| 遗漏风险项数 | 8项 | 1项 | -88% |

## Readme

<!-- 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.


---
*Source: https://skills.yangsir.net/skill/gh-convex-optimize*
*Markdown mirror: https://skills.yangsir.net/api/skill/gh-convex-optimize/markdown*