canary

Monitor deployed URLs for console errors, performance regressions, and page failures against baselines.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/JeremiahEllington/NoahEllington --skill canary-jeremiahellington
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/JeremiahEllington/NoahEllington/tree/main/.claude/skills/canary
Command: npx skills add https://github.com/JeremiahEllington/NoahEllington --skill canary-jeremiahellington

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-deploy canary monitoring helps catch production issues early by watching the live app for console errors, performance regressions, and page failures, and by comparing results to pre-deploy baselines.

Core Features & Use Cases

  • Detect issues quickly after deploy by monitoring errors, performance, and page failures.
  • Take periodic screenshots, compare against baselines, and alert on anomalies.
  • Support baseline capture, page discovery, and targeted monitoring across multiple routes.

Quick Start

Run the canary monitor on the deployed URL and follow the prompts to configure duration, pages, and baseline options.

Frequently Asked Questions about canary

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

FAQPage Schema
How do I monitor a URL for console errors and performance regressions after deployment?

Post-deploy canary monitoring tracks a live URL to detect console errors, performance regressions, and page failures by comparing live results against pre-deploy baselines. It collects screenshots, console output, and performance metrics to alert on anomalies.

What is post-deploy canary monitoring and when do I need it?

Post-deploy canary monitoring is the process of watching a live application for errors and performance regressions immediately after deployment. You need it to catch production issues early by comparing live telemetry against pre-deploy baselines.

Can I capture pre-deploy baselines for multiple routes before running canary monitoring?

Yes, canary monitoring supports baseline capture and page discovery modes across multiple routes. You can configure targets to collect textual snapshots, screenshots, and performance metrics as a baseline before deployment.

How do I set up automated post-deploy monitoring with screenshots and console output collection?

Run the canary monitor on your deployed URL and follow the prompts to configure duration, pages, and baseline options. It uses the browse daemon to automatically collect screenshots, console output, and performance telemetry.

Does canary monitoring work without external dependencies?

Yes, the canary monitoring skill operates with no external dependencies. It uses the built-in browse daemon to route and collect page telemetry, requiring only a deployed URL to begin monitoring.

What are the limitations of using screenshots and baselines for post-deploy monitoring?

Canary monitoring relies on comparing live results to pre-deploy baselines, so dynamic content changes may trigger false positives. It is best suited for detecting console errors, performance regressions, and page failures rather than functional logic changes.