canary

Monitors deployed web apps for console errors, performance regressions, and page failures using browser automation.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/TarunTeja44/portfolio --skill canary-tarunteja44
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/TarunTeja44/portfolio/tree/main/.agents/skills/canary
Command: npx skills add https://github.com/TarunTeja44/portfolio --skill canary-tarunteja44

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploys that pass CI can still break in production due to missing environment variables, stale CDN caches, or slow migrations. This Skill watches your live app in the critical first minutes after a deploy, catching regressions before users do. ## Core Features & Use Cases - Baseline Capture: Take pre-deploy screenshots, console error counts, and load times to compare against after shipping. - Continuous Monitoring Loop: Checks pages every 60 seconds for a configurable duration (1-30 minutes), alerting only on changes that persist across consecutive checks. - Severity-Based Alerts: Classifies issues as CRITICAL (page load failure), HIGH (new console errors), MEDIUM (2x performance regression), or LOW (broken links), each backed by screenshot evidence. - Use Case: After deploying to production, run the canary against your URL for 10 minutes. It auto-discovers your main navigation pages, watches them, and produces a health report with a HEALTHY, DEGRADED, or BROKEN verdict. ## Quick Start Monitor my production site at https://myapp.com for 10 minutes after this deploy and alert me if any console errors or performance regressions appear.

Frequently Asked Questions about canary

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

FAQPage Schema
How do I monitor my website after a deployment?

Run the canary command with your production URL to start a 10-minute monitoring loop. It checks each page every 60 seconds for new console errors, load failures, and performance regressions, alerting only on issues that persist across consecutive checks.

How to capture a baseline before deploying changes?

Run the canary with the --baseline flag before deploying. It records screenshots, console error counts, and page load times for each page into a baseline.json manifest, which later monitoring runs compare against to detect regressions.

Can I monitor specific pages instead of the whole site?

Yes, pass a comma-separated page list with the --pages flag, such as /,/dashboard,/settings. Without it, the skill auto-discovers the top internal navigation links and asks you to confirm which pages to watch.

What counts as a performance regression in canary monitoring?

A page whose load time exceeds 2x its baseline is flagged as a MEDIUM severity regression. Thresholds are relative to your own baseline rather than absolute industry numbers, and alerts require the pattern to persist across at least two consecutive checks.

Does canary monitoring modify my production code?

No, the skill is strictly read-only. It observes pages, takes screenshots, and reports findings, but never modifies code unless you explicitly ask it to investigate and fix a detected issue.