convex-optimize
This skill audits an existing Convex app with a single scored readiness report, then acts on it: upgrading stale @convex-dev components, closing observability gaps by installing production error capture, and applying each prioritized fix only after explicit confirmation. It ranks security and data-loss risks above style, re-runs the assessment afterwards and shows the score delta. It is ideal before a launch, after a major refactor, or during ongoing maintenance of a live production app.
npx skills add https://github.com/convex/agent-skills --skill convex-optimizeBefore / After Comparison
1 组Before launch you had to manually sweep authz, code review, advisor and runtime insights, re-running overlapping checks, while separately tracking stale component versions and whether production errors were captured at all — easy to miss items.
This skill produces one scored, deduped report, ranks security and data-loss risks first, folds stale components and monitoring gaps into the same plan, then applies confirmed fixes and shows the re-assessed score delta.
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.
User Reviews (0)
Write a Review
No reviews yet
Statistics
User Rating
Rate this Skill