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.