SKILL DETAIL
convex-monitor
get-convex/agent-skills/convex-monitor
This skill watches for the next dev/prod error or request in a Convex app and reacts to it. It blocks on the next typed event instead of polling, racing local error logs, deployment subscriptions, and Sentinel prod-error rows, returning the first to fire (or a quiet heartbeat). The workflow involves calling wait_for_event with project_dir, event_kinds, and timeout_ms; then handling events based on their kind (e.g., convex_error, prod_error, feature_request, or quiet). In environments without a blocking MCP, the skill uses a poll loop with the same event contract.
Installation
npx skills add https://github.com/get-convex/agent-skills --skill convex-monitor
Fichiers du skill
SKILL.md
Dernière synchronisation · 29 août 2026
SKILL.md›
---
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.