Convex Monitor
Block on the next Convex dev/prod error or request with wait_for_event instead of polling — then react
- What
- Block on the next Convex dev/prod error or request with wait_for_event instead of polling — then react
- Cost
- Free
- Needs
- a Convex project (see the repo README for setup); a Convex deployment; the official Convex MCP; optionally Sentinel for prod error events
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — teaches the "wait for the event, don't poll" pattern: block on the next typed event (convex dev/prod error, next request) with `wait_for_event` instead of polling, then react (fix it, triage it, build it) — racing local error logs, deployment subscriptions and Sentinel prod-error rows, first to fire wins. Where a harness has no blocking MCP, a poll loop runs with the SAME event contract — same behavior, different mechanism. Distinct from `get-convex-convex-insights` (lot 32): insights = interrogate logs/health on demand; monitor = REACTIVE loop on events. By @get-convex, listed here with credit to its creator. Honest caveats: requires a Convex project and deployment (free tier exists); prod events need a deployed cloud app plus Sentinel; event schema is fixed and versioned. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Convex project (see the repo README for setup); a Convex deployment; the official Convex MCP; optionally Sentinel for prod error events Install "Convex Monitor" for me. Give my agent the reactive monitoring workflow: block on the next typed event with wait_for_event (convex dev/prod error, next request, prod error, feature request, quiet heartbeat) and react accordingly, falling back to a poll loop with the same event contract where blocking MCP is unavailable Repository: https://github.com/get-convex/agent-skills/blob/main/skills/convex-monitor/SKILL.md 1. Fetch the SKILL.md file for the get-convex-agent-skills-convex-monitor skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "get-convex-agent-skills-convex-monitor". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. have a deployment to watch, install the Convex MCP). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.