convex-monitor — Claude Code skill: catch the next Convex error
This skill blocks on the next event in a Convex app — a dev error, a prod error or a feature request — and hands it to the agent.
npx skills add convex/agent-skills --skill convex-monitor -a claude-codeWhat convex-monitor does
Instead of polling, the agent calls wait_for_event with {project_dir, event_kinds, timeout_ms} and waits. Local error logs, deployment subscriptions and Sentinel prod-error rows race each other, and the first one to fire wins. If nothing happens, you get a quiet heartbeat.
What comes next depends on the kind. convex_error or next_error — decode and fix. prod_error — triage through sentinel, then fix. feature_request — build it. quiet — loop again. The event schema is fixed and versioned, so the same trigger always yields the same typed event.
Prod events need a deployed cloud app plus Sentinel, so that path is off the table without them. On harnesses with no blocking MCP, Copilot cloud for instance, the skill falls back to a poll loop with the same event contract — same behaviour, different mechanism.
What it helps with
- catch the next dev error and fix it right away
- triage a prod error through Sentinel
- stop polling logs by hand and block on an event instead
- receive a feature request and build it in the same loop
- survive a quiet stretch and go back to waiting
Example prompts for the agent
- call wait_for_event for the project and wait for the next error
- wait for a prod_error event and triage it through sentinel
- set a wait on feature_request and build whatever arrives
How to install convex-monitor
1Skills CLI (Vercel)
npx skills add convex/agent-skills --skill convex-monitor -a claude-code2Manually: put the files in place
~/.claude/skills/convex-monitor/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/convex-monitor/
1Skills CLI (Vercel)
npx skills add convex/agent-skills --skill convex-monitor -a codex2Manually: put the files in place
.agents/skills/convex-monitor/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add convex/agent-skills --skill convex-monitor -a cursor2Manually: put the files in place
.cursor/skills/convex-monitor/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install convex/agent-skills convex-monitor2Manually: put the files in place
.github/skills/convex-monitor/SKILL.md1Skills CLI (Vercel)
npx skills add convex/agent-skills --skill convex-monitor -a gemini-cli2Platform CLI
gemini skills install https://github.com/convex/agent-skills --path skills/convex-monitorManually: put the files in place
.devin/skills/convex-monitor/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add convex/agent-skills --skill convex-monitor -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about convex-monitor
How do I install convex-monitor in Claude?
Run npx skills add convex/agent-skills --skill convex-monitor -a claude-code. The skill then lives at ~/.claude/skills/convex-monitor/SKILL.md.
What does convex-monitor do?
It blocks on the next typed event in a Convex app instead of polling: a dev error, a prod error or a feature request. The first event to fire goes to the agent for handling.
What do prod events require?
Events of kind prod_error need a deployed cloud app and Sentinel. Without those, the skill still catches local errors and feature requests.
Source text
SKILL.md · Apache-2.0
---
name: convex-monitor
description: "Watch for the next dev/prod error or request in a Convex app and react to it."
---
<!-- GENERATED from convex-agents content/capabilities/monitor.json — do not edit by hand. -->
# Watch for the next thing to react to
Block on the next typed event instead of polling. Races local error logs, deployment subscriptions, and Sentinel prod-error rows; returns the first to fire (or a quiet heartbeat).
## Workflow
1. Call `wait_for_event` with {project_dir, event_kinds, timeout_ms}.
2. On kind=convex_error/next_error: decode and fix it. On kind=prod_error: triage (see sentinel) and fix. On kind=feature_request: build it. On kind=quiet: loop.
3. Where a harness has no blocking MCP (e.g. Copilot cloud), the pack runs a poll loop with the SAME event contract — same behavior, different mechanism.
## Rules
- Prefer the blocking tool; fall back to a poll loop only where blocking MCP is weak.
- The event schema is fixed and versioned — the same trigger yields the same typed event.
- Prod events (kind=prod_error) require a deployed cloud app plus Sentinel.
© convex · Apache-2.0 · convex/agent-skills