convex-monitor Skill for Claude Code: What It Does and How to Install It
Makes Claude wait for the next error or request in your Convex app and then react to it.
- Installs
- 38.3K
- on skills.sh
- Stars
- 68
- on GitHub
- Updated
- Oct 2026
- last repo commit
This skill makes Claude wait for the next event from a Convex app instead of polling for it. It races local error logs, deployment subscriptions and Sentinel production-error rows, and takes whichever fires first, or a quiet heartbeat. Then it reacts: it decodes and fixes a dev error, triages a production error, builds a feature request, or waits again.
It calls a tool named wait_for_event with project_dir, event_kinds and timeout_ms. SKILL.md does not say which server provides that tool, and the Convex MCP docs list 12 tools, none of them wait_for_event. Production events need a deployed cloud app plus Sentinel. Its folder holds only SKILL.md.
Good for
- Convex developers who want Claude to react to dev errors as they happen
- Teams that have Sentinel and want production errors to reach Claude
Install convex-monitor
Claude Code
- 1
Copy this prompt.
Install the convex-monitor skill in Claude Code. Run this command: npx skills add https://github.com/convex/agent-skills --skill convex-monitor Then check that it loaded and tell me how to use it.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Requires Node.js.
SKILL.md names no other skill it needs. It also mentions convex-sentinel as optional hand-offs; install those separately if you want them. Convex's docs say the skills CLI installs skills into .agents/skills/ in your project. The "All Convex skills" command installs every skill in the repo, which has 33 skill folders. One of them, convex-improve-convex-plugin, is listed in the Convex docs as sending your coding session's transcript to the Convex team. Run this skill with /convex-monitor in Claude Code or $convex-monitor in Codex, or let the agent pick it when the task fits. This skill works on your project folder, so this page offers no Claude app upload route.
Built from the package data we hold. Not yet tested by us.
What's in the skill
When it loads
Watch for the next dev/prod error or request in a Convex app and react to it.
Sections in SKILL.md
- Workflow
- Rules
Key facts
- Installs on skills.sh
- 38,270 (Nov 2, 2026)
- Last repo commit
- Oct 29, 2026
- Audits on skills.sh
- Gen Agent Trust Hub: pass, Socket: pass, Snyk: pass
What it includes
Calls wait_for_event with project_dir, event_kinds and timeout_ms until one fires
SKILL.md names no server for this tool.
Network ·
Wait for an eventOn convex_error or next_error, decodes the error and fixes it
Write ·
React to a dev errorOn prod_error, triages it (see sentinel) and fixes it
Needs a deployed cloud app plus Sentinel.
Write ·
React to a production errorOn feature_request, builds the requested feature
SKILL.md does not say where feature requests come from.
Write ·
React to a feature requestOn kind=quiet, goes back to waiting
Where a harness has no blocking MCP, such as Copilot cloud, a poll loop with the same event contract is used instead.
Loop on quiet
From the official docs
Permissions
Medium risk
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
It acts on events without a stated approval step
SKILL.md says to decode and fix errors and to build feature requests. It does not describe a confirmation step. Run it on a branch and review the changes. github.com
The wait_for_event tool has no named source
SKILL.md does not say which server provides it, so check what your setup connects before relying on it. github.com
Security advisories
No published security advisories as of Nov 2, 2026.
Technical details
| Turning on read-only | SKILL.md defines no read-only mode. |
|---|---|
| Sign-in and keys | SKILL.md names no credentials. |
| Scopes |
|
Questions
What does convex-monitor do?
It makes Claude wait for the next typed event from a Convex app, such as a dev error, a production error or a feature request, and then act on it. SKILL.md describes it as blocking on an event instead of polling.
What does it need?
A tool called wait_for_event. SKILL.md does not say which server or plugin provides it. Production events also need a deployed cloud app with Sentinel installed, which convex-sentinel sets up.
Which events can it react to?
SKILL.md lists convex_error and next_error for dev errors, prod_error for production errors, feature_request, and quiet when nothing happened.
How do I install it?
Use the install box at the top of this page. Add convex-sentinel separately if you want production events. The wait_for_event tool the skill calls is not part of this repo's skill folder. Run it with /convex-monitor in Claude Code or $convex-monitor in Codex.
Is it safe?
It reacts to events by editing your project, and for feature requests by building them. SKILL.md does not say who can raise a feature request. Our advice: run it on a branch and watch the first few events.
How is it different from convex-sentinel?
convex-sentinel sets up the capture of production errors into your own deployment. convex-monitor is the part that waits for those events and others and reacts.
Is it official?
It is in the convex/agent-skills repo under the Convex GitHub organisation, which is the vendor's own repo.
Information
updated Nov 2, 2026
- Repository
- convex/agent-skills
- Folder
skills/convex-monitor
Sources
Docs, issue trackers and discussions this page is built from.
Show all 5Hide
- convex/agent-skills README · github.com
- skills CLI commands · github.com
- Convex docs: Agent Skills · docs.convex.dev
- convex-monitor SKILL.md · github.com
- Convex docs: MCP server · docs.convex.dev