get-convex/agent-skills

convex-monitor

Watch for the next dev/prod error or request in a Convex app and react to it.

All-time #1024 Trending #522 Hot #5898 First seen Aug 1, 2026
8-week activity · all time api

Installation

$ npx skills add get-convex/agent-skills --skill convex-monitor

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from get-convex/agent-skills · top by installs.

npx skills add get-convex/agent-skills

Browse all from get-convex/agent-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 53
License LICENSE
Default branch main
Open issues 2
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents github-copilot

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,108 B
  • docs SUMMARY.md 99 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 18,616 installs

SKILL.md

<!-- 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 waitforevent with {projectdir, eventkinds, timeout_ms}.
  2. On kind=convexerror/nexterror: decode and fix it. On kind=proderror: triage (see sentinel) and fix. On kind=featurerequest: 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.