canary

Monitors production deployments with browser or HTTP health checks and reports verdicts.

6|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/greglas75/zuvo --skill canary-greglas75
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/greglas75/zuvo/tree/main/skills/canary
Command: npx skills add https://github.com/greglas75/zuvo --skill canary-greglas75

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After deploying to production, teams need to verify the release is healthy before considering it done. This Skill automates post-deploy monitoring by repeatedly checking a production URL for HTTP failures, console errors, and slow response times, then issuing a clear HEALTHY, DEGRADED, or BROKEN verdict. ## Core Features & Use Cases - Browser or HTTP-only monitoring: Uses Playwright or Chrome DevTools when available for console error capture and screenshots, and falls back to curl-based HTTP checks in degraded mode. - Configurable monitoring loops: Set duration (1m-30m), check interval, and error thresholds, or run a single quick check with --quick. - Verdicts with rollback guidance: Produces HEALTHY/DEGRADED/BROKEN verdicts, writes summary.json reports with p95 response times, compares against prior baselines, and suggests platform-specific or git-native rollback commands when broken. - Use Case: After shipping a release, run the canary against https://myapp.com for 10 minutes; if console errors exceed the threshold, receive a BROKEN verdict plus a concrete git revert command. ## Quick Start Run the canary skill against https://myapp.com with a 10 minute duration to verify the latest deployment is healthy.

Frequently Asked Questions about canary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor a production deployment after release?

Run the canary skill with your production URL, for example with a 10 minute duration and 60 second interval. It performs repeated health checks for HTTP status, console errors, and response time, then reports a HEALTHY, DEGRADED, or BROKEN verdict.

How to check for browser console errors after deployment?

When Playwright or Chrome DevTools tools are available, the skill captures Error-level console messages on every check cycle. Each new error counts as a HIGH alert and accumulates toward the --max-errors threshold that determines the final verdict.

Can I run post-deploy health checks without a browser?

Yes. If no browser automation tools are detected, the skill switches to degraded mode using curl for HTTP status and response time checks. Console error capture and screenshots are unavailable in this mode, and the output is annotated accordingly.

What happens when the canary verdict is BROKEN?

On a BROKEN verdict the skill prints a rollback command. If a deployment platform was detected it uses that platform's rollback command, otherwise it reads memory/last-ship.json for the release commit SHA and suggests git revert followed by git push.

What are the limitations of the monitoring duration and interval?

Duration must be between 1 and 30 minutes; values outside this range stop execution with a validation error. In non-interactive environments the skill defaults to a single one-shot check unless --duration is explicitly passed.