convex-launch-readiness

Aggregates Convex audit findings into a scored, deduplicated launch-readiness report with an ordered fix plan.

9.4k|1.5k|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/openclaw/clawhub --skill convex-launch-readiness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convex-launch-readiness
Source: https://github.com/openclaw/clawhub/tree/main/.agents/skills/convex-launch-readiness
Command: npx skills add https://github.com/openclaw/clawhub --skill convex-launch-readiness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before shipping a Convex backend, teams run separate authz, code-review, performance, and log audits and end up with four disconnected reports, duplicated findings, and no clear priority order. This Skill composes all audit passes into one scored, deduplicated readiness report with an ordered fix plan.

Core Features & Use Cases

  • Unified audit composition: Runs the convex-authz, convex-reviewer, convex-advisor, and convex-insights passes, skipping any whose preconditions (deployment, traffic) are not met and stating which were skipped.
  • Deduped, auditable scoring: Normalizes each finding to a function/table identity so the same defect seen from code and deployment loci collapses to one, then computes a reproducible score (100 minus per-severity penalties) with the formula printed.
  • Prioritized fix dispatch: Groups findings into blockers, should-fix, and nice-to-have, then dispatches accepted fixes to the owning fixer capabilities and re-runs affected passes to show the score delta.
  • Use Case: Before promoting a Convex app to production, ask for a launch-readiness report to get a single score, a ranked list of authz and performance defects, and the exact sequence of fixer capabilities to run next.

Quick Start

Run a launch-readiness report on my Convex backend and show the score, ranked findings, and ordered fix plan.

Frequently Asked Questions about convex-launch-readiness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my Convex backend is ready for production?

Run the launch-readiness report, which executes the authz, reviewer, advisor, and insights audit passes and combines their findings into one scored report. It ranks findings by severity and ends with an ordered fix plan starting with data-loss and authz issues.

How is the Convex readiness score calculated?

The score starts at 100 and subtracts per confirmed finding by severity: high minus 15, medium minus 5, low minus 1, floored at 0. The exact formula and per-class breakdown are printed so the number is reproducible, and plausible-only findings do not move the score.

Does the readiness report work without a deployed Convex deployment?

Yes, but it produces a code-only score that is explicitly labeled as such. The advisor and insights passes require a live deployment with traffic, so they are recorded as skipped and listed as a coverage gap in the report header.

How are duplicate findings from different Convex audits handled?

Each finding is normalized to a function/table identity before deduplication, so the same defect reported at a code locus and a deployment locus collapses into one entry. The higher-confidence source is kept and nothing is dropped silently.

Does the launch-readiness check fix the issues it finds?

No, it only decides what to fix and in what order. Each finding names a fixCapability, and fixes are dispatched on request to the owning fixer capabilities, after which affected passes are re-run to show the score delta.