convex-performance-audit

Name: convex-performance-audit
Availability: InStock
Author: liminal-ai

Diagnose Convex app performance issues by identifying the strongest signal.

1|1|Updated Apr 13, 2026

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

Ready to run

npx skills add https://github.com/liminal-ai/liminal-build --skill convex-performance-audit-liminal-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: convex-performance-audit
Source: https://github.com/liminal-ai/liminal-build/tree/main/.agents/skills/convex-performance-audit
Command: npx skills add https://github.com/liminal-ai/liminal-build --skill convex-performance-audit-liminal-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Diagnoses Convex performance issues across hot-path reads, write contention, subscription cost, and function limits, enabling targeted improvements when a feature is slow or expensive.

Core Features & Use Cases

Gather signals from CLI insights, dashboards, or code audits to identify the strongest performance problem class.
Map signals to Convex reference patterns (hot-path, OCC conflicts, subscription cost, function budgets) and prescribe concrete, minimal fixes.
Apply fixes across related functions and reviews to prevent regressive hotspots.

Quick Start

Run a Convex performance audit on your project to identify the strongest signal and implement the smallest high-impact fix first.

Frequently Asked Questions about convex-performance-audit

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

FAQPage Schema

How do I diagnose slow Convex queries and high bytes read?▼

To diagnose Convex performance issues, gather signals from CLI insights and dashboards to identify the strongest problem class, such as hot-path reads or subscription costs. The workflow then maps these signals to reference patterns for targeted fixes.

What causes frequent mutation retries and write contention in Convex?▼

Frequent mutation retries in Convex are typically caused by OCC (optimistic concurrency control) conflicts during write contention. An audit identifies these signals and prescribes minimal, scoped fixes across related functions to reduce conflicts.

How can I reduce high subscription and reactivity costs in my Convex app?▼

Reduce high Convex subscription costs by auditing reactivity across UI, functions, and queries. The audit identifies the strongest performance signal and guides targeted improvements to prevent regressive hotspots and lower overall subscription expenses.

What is the best way to fix Convex hot-path reads and function limits?▼

The best way to fix Convex hot-path issues is to map CLI and dashboard signals to reference patterns, then apply the smallest high-impact fix first. This targeted workflow ensures safe changes while addressing function budgets and read limits.

Why does my Convex feature remain slow after initial code refactoring?▼

A Convex feature may remain slow if refactoring misses the strongest performance signal or creates regressive hotspots. A structured audit validates scoped fixes across related functions and reviews to ensure the changes actually resolve the bottleneck.

Can I audit a Convex project for performance without prior CLI insights?▼

Yes, you can audit Convex performance using code audits if CLI insights are unavailable. The workflow accommodates multiple signal sources to identify problem classes like subscription cost or OCC conflicts and guide targeted improvements.