convex-insights

Query Convex deployment logs and health insights through the official MCP tools.

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/Tehzeeb07/CodeRush --skill convex-insights-tehzeeb07
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: convex-insights
Source: https://github.com/Tehzeeb07/CodeRush/tree/main/.agents/skills/convex-insights
Command: npx skills add https://github.com/Tehzeeb07/CodeRush --skill convex-insights-tehzeeb07

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Investigating failures, slow functions, and deploy regressions in a running Convex app requires knowing the right log filters and tool limits, and raw log dumps are hard to act on. This Skill turns natural-language operational questions into scoped, evidence-backed queries against the official Convex MCP read tools. ## Core Features & Use Cases - Failures View: Fetches a bounded log window and groups errors by function and message, returning counts plus a representative stack trace. - Health View: Surfaces typed 72-hour read-limit and OCC events from the insights tool, routing perf and cost root-causing to the advisor skill. - Trace View: Filters logs client-side to a single requestId or function to explain why one specific call failed. - Use Case: After a deploy, ask whether the new version broke anything; the Skill compares failure onset timestamps against the deployment version and returns a dashboard deep link for one-click verification. ## Quick Start Ask the agent to check whether any Convex functions started failing after the latest deploy and show the evidence with a dashboard link.

Frequently Asked Questions about convex-insights

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

FAQPage Schema
How do I query Convex logs to find failing functions?▼

Fetch a bounded recent window with the logs tool using a history count and JSONL output, then filter client-side by failure status and group by function and error message. The Convex logs tool has no server-side status or function filter, so local filtering is required.

How to check if a Convex deploy broke my app?▼

Compare the failure onset timestamps from recent logs against the deployment version reported by the status tool. This correlates errors with the deploy rather than asserting causation, and a dashboard deep link lets you verify in the Convex dashboard.

Can I filter Convex logs by function name or time range?▼

No, the logs tool only accepts a history count, success flag, JSONL output, and prod or deployment selectors. You must fetch a bounded recent window and filter by function, requestId, or timestamp on the client side.

Does Convex insights work on local or self-hosted deployments?▼

No, the insights tool is cloud-only and requires user authentication against a cloud dev or prod deployment. It surfaces typed 72-hour read-limit and OCC conflict events but has no function-level filter.

Why does querying Convex logs return empty or confusing results?▼

Empty results usually come from guessing function names that do not exist in the deployment. Run functionSpec first to discover real function identifiers and status to confirm the deployment before filtering logs.