Agent Skills
› openclaw/clawhub
› convex-optimize
convex-optimize
GitHub对现有 Convex 应用进行审计与优化。通过调用 launch-readiness 获取评分报告，执行组件升级和可观测性配置（如 sentinel），生成包含安全、数据丢失优先级的修复计划，并在用户确认后实施，最后重新评估以展示改进效果。
Trigger Scenarios
需要优化现有 Convex 应用的性能或安全性
希望升级过时的 Convex 组件并设置监控
请求对已部署的 Convex 应用进行全面审计
Install
npx skills add openclaw/clawhub --skill convex-optimize -g -y
SKILL.md
Frontmatter
{
"name": "convex-optimize",
"description": "Audit and optimize an existing Convex app: security, scale, upgrades, observability."
}
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
- Detect the app: a
convex/directory, the schema, and whether it's an anonymous or cloud deployment. - 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. - UPGRADE: run
check-updatesagainst the pinned@convex-dev/*components and fold stale-component (staleness-class) findings into the same plan. - OBSERVABILITY: if the readiness report flagged an observability gap (no prod error capture), offer to install
sentinel. - 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.
- 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.
Version History
- d6a8c68 Current 2026-08-20 02:44
