Skip to main content
skill CX Codex

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.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add convex/agent-skills --skill convex-monitor -a claude-code
Open on GitHub

What 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-code

2Manually: put the files in place

~/.claude/skills/convex-monitor/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/convex-monitor/

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

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set32

convex-crons Adds recurring scheduled jobs to Convex applications. Useful when you need to schedule backend maintenance and periodic cleanups. CX Codex +1 36,000installs convex-env This skill sets and wires Convex deployment environment variables and secrets. Use it when actions need deployment-specific values without putting secrets in code. CX Codex +1 36,000installs convex-seed Populates Convex database tables with sample rows or imports external datasets. Useful when preparing dev environments without manual data entry. CX Codex +1 35,800installs convex-verify convex-verify tests a Convex feature with seeded data, multiple mocked identities, and negative authorization checks. Use it for a specific feature you have built or changed. CX Codex +1 35,800installs convex-billing Adds Stripe payments and subscriptions to a Convex app using @convex-dev/stripe with checkout sessions, webhooks, and subscription gating. CX Codex +1 35,800installs convex-domains Walks your agent through DNS records at your registrar, attaching the domain to a Convex app, and rebinding the auth origin. CX Codex +1 35,800installs convex-launch-readiness Runs four Convex audits into one readiness report with a score and an ordered fix plan. Useful when the backend is about to ship and you need to know what to fix first. CX Codex +1 35,900installs convex-explain-app Maps an existing Convex backend using schema and exported functions. It helps you understand data models, public APIs, and auth before making changes. CX Codex +1 35,900installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor