Analyzed Aug 1, 2026
get-convex/agent-skills
convex-monitor
Watch for the next dev/prod error or request in a Convex app and react to it.
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.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill shoul…
3.7K installsUse when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge F…
1.7K installsReact Native and Expo best practices for building performant mobile apps. Use when building Rea…
1.3K installsAlert by webhook/email on web changes — use for "monitor/watch/track/alert me when": recurring …
33 installsContinuously track the web for changes on a recurring cadence.
22 installsAlert by webhook/email on web changes — use for "monitor/watch/track/alert me when": recurring …
97 installsSecurity audits
Partner security reviews for this skill.
Analyzed Aug 1, 2026
Analyzed Aug 1, 2026
0 alerts
Also in this package
Other skills from get-convex/agent-skills · top by installs.
npx skills add 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.
Repository health
main
Skill metadata
Parsed from SKILL.md frontmatter.
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md1,108 B -
docs
SUMMARY.md99 B
History
- First seen on skills.sh
- 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
- Call
waitforeventwith {projectdir, eventkinds, timeout_ms}. - 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.
- 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.