SECURITY REVIEW
Not yet assessed
Review the original instructions and requested permissions before installing.
No security review is available for this catalog entry yet.
Devops · Backend / AGENT SKILL
convex-sentinel
0
Set up Sentinel production error capture in a Convex deployment.
Set up Sentinel production error capture in your own Convex deployment.
Understand the trade-offs.
SKILL QUALITY
Not yet assessed
How clearly the skill guides your agent, how complete its workflow is, and how you can check the outcome.
No quality assessment is available for this catalog entry yet.
The full skill.
Original instructions from the publisher’s SKILL.md
<!-- GENERATED from convex-agents content/capabilities/sentinel.json — do not edit by hand. --> # Capture production errors in your own deployment Install `@convex-dev/sentinel` to capture production errors (server function failures, client JS/React crashes, OCC and scale signals) into a table in the user's OWN deployment, redacted at write time, then react to new ones. Data never leaves the user's deployment. ## Workflow 1. Install the component: `app.use(sentinel)` in `convex/convex.config.ts`. 2. Wire the client SDK: a React error boundary plus `window.onerror`/`unhandledrejection` and breadcrumbs. 3. Redaction runs at write time and is on by default (default-deny on secret key names and value patterns). 4. Read recent errors with the Convex CLI (`convex data`, `run-once-query`); react to new ones via the monitor's `prod_error` event. 5. Optionally enable the self-healing cron: `triage` classifies each error and, for recurring non-transient ones, hands it to ai-runner to open a fix PR. ## Rules - Redaction is mandatory and on by default — never store raw secrets; the agent's reads reach the model provider. - Data stays in the user's deployment; never send it to a third party. - Sample and cap to control volume and cost. - Capturing PROD errors needs a deployed cloud app; install works anonymously.