convex-performance-audit

Audit Convex hot-path reads, subscriptions, and write contention.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/flvvius/cue --skill convex-performance-audit-flvvius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convex-performance-audit
Source: https://github.com/flvvius/cue/tree/main/packages/backend/.agents/skills/convex-performance-audit
Command: npx skills add https://github.com/flvvius/cue --skill convex-performance-audit-flvvius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps diagnose and optimize Convex apps that feel slow, read too much data, invalidate too often, or hit execution and transaction limits.

Core Features & Use Cases

  • Hot-path read auditing: Identifies broad scans, unnecessary joins, and oversized payloads on frequently used queries.
  • Subscription and invalidation tuning: Reduces excessive useQuery and usePaginatedQuery cost, especially on low-freshness or broad reactive views.
  • Write contention and budget fixes: Addresses OCC conflicts, no-op writes, and large mutations that need batching or scheduling.
  • Use case: A Convex dashboard shows high bytes read and sluggish list views, and this Skill traces the full read/write path to suggest the smallest high-impact fix.

Quick Start

Ask the assistant to audit the Convex feature for performance issues and recommend the smallest safe 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 optimize slow Convex queries and reduce high bytes read?

To optimize slow Convex queries, audit hot-path reads for broad scans, unnecessary joins, and oversized payloads. Tracing the full read path identifies the smallest high-impact fix to reduce bytes read and improve list view responsiveness.

Why does my Convex app have excessive subscription invalidation and how do I fix it?

Excessive subscription invalidation in Convex happens when reactive views trigger too many updates. Tuning useQuery and usePaginatedQuery calls on low-freshness views reduces invalidation overhead and cuts unnecessary reactive costs.

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

Resolve Convex OCC conflicts by auditing write contention and eliminating no-op writes. Large mutations nearing transaction limits can be fixed through batching or scheduling to avoid execution budget errors.

What's the best way to fix Convex functions hitting transaction or execution limits?

Fix Convex functions hitting limits by tracing write paths and applying guardrailed fixes like batching large mutations. This ensures mutations stay within transaction budgets while preserving migration-safe behavior across sibling functions.

Can I audit Convex paginated queries for performance without breaking existing behavior?

Auditing Convex paginated queries applies guardrailed fixes that preserve migration-safe behavior across sibling functions. This ensures subscription tuning reduces costs without breaking existing reactive data flows.