convex-performance-audit

Audit Convex apps to identify performance bottlenecks and output a migration-safe remediation plan.

1|Updated Feb 7, 2026

Search Tags:#performance #audit #convex #hot-path #occ-conflicts #subscription-cost

Ready to run

npx skills add https://github.com/MarcoDava/MockCortex --skill convex-performance-audit-marcodava

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: convex-performance-audit
Source: https://github.com/MarcoDava/MockCortex/tree/main/frontend/.agents/skills/convex-performance-audit
Command: npx skills add https://github.com/MarcoDava/MockCortex --skill convex-performance-audit-marcodava

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Diagnose and fix performance problems in Convex applications, one problem class at a time.

Core Features & Use Cases

Identify hot-path reads, write contention, and subscription overhead that hamper performance.
Map signals from insights to targeted references and guardrails to guide fixes.
Apply a structured remediation workflow that scales across related functions and backfills.

Quick Start

Begin the audit from the strongest signal available (insights, deployment health, or code audit) to identify the primary performance bottleneck and start the remediation.

Frequently Asked Questions about convex-performance-audit

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

FAQPage Schema

How do I audit my Convex app for performance bottlenecks?▼

To audit a Convex app, start from the strongest signal available such as deployment health or insights to identify the primary performance bottleneck and begin remediation. A structured workflow maps these signals to targeted fixes.

Why does my Convex app have slow pages and high read/write patterns?▼

Slow pages and high read/write patterns in a Convex app are typically caused by hot-path reads, write contention, or subscription overhead. An audit identifies these specific bottlenecks and maps them to guardrails for fixes.

How do I resolve OCC conflicts and write contention in Convex?▼

Resolving OCC conflicts and write contention requires identifying the problematic write patterns through signals. A structured audit maps these contention signals to targeted references and guardrails to guide safe remediation.

What is the best way to reduce subscription overhead in Convex?▼

Reducing subscription overhead involves identifying the overhead through insights or code audits, then applying a structured remediation workflow that scales fixes across related functions and backfills for a migration-safe plan.

Can I use convex insights to guide a performance remediation plan?▼

Yes, you can begin the audit directly from convex insights signals. The workflow maps those insights to targeted references and guardrails, outputting a migration-safe remediation plan for your application.

Does a Convex performance audit provide a migration-safe remediation plan?▼

Yes, the audit applies a structured remediation workflow that scales across related functions and backfills, ultimately outputting a migration-safe remediation plan to fix hot-paths, OCC conflicts, and subscription budgets.