canary

Monitors deployed apps for console errors, performance regressions, and page failures via browse daemon screenshots and baselines.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Intension-us/attention-diagnostic --skill canary-intension-us
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/Intension-us/attention-diagnostic/tree/main/.claude/skills/gstack/canary
Command: npx skills add https://github.com/Intension-us/attention-diagnostic --skill canary-intension-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-deploy canary monitoring catches issues in production by watching the live app for console errors, performance regressions, and page failures, using the browse daemon to take periodic screenshots and compare against baselines.

Core Features & Use Cases

  • Continuous post-deploy monitoring with baseline comparisons and anomaly alerts.
  • Screenshots, console checks, and performance measurements across multiple pages.
  • Telemetry-friendly or opt-in data collection to improve reliability over time.

Quick Start

Run the canary against your app URL after deploy to start a 10-minute health check that captures baselines and reports anomalies.

Frequently Asked Questions about canary

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

FAQPage Schema
How do I monitor my app for performance regressions after a production deployment?

You can monitor your app for performance regressions after deployment by running an automated canary check against your live URL to capture baseline metrics, measure load times, and trigger alerts on detected anomalies.

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

Post-deploy canary monitoring is the process of watching a live app for console errors, page failures, and performance regressions. You need it immediately after deployments to catch production issues before they affect users.

Can I capture a performance baseline and compare live app pages against it?

Yes, you can capture a performance baseline for your live app pages and compare subsequent measurements against it. The monitoring daemon takes periodic screenshots and measures load times to detect regressions.

How do I check for console errors across multiple pages after releasing?

To check for console errors across multiple pages after releasing, run an automated post-deploy monitoring session against your app URL. The daemon supports per-page monitoring to capture screenshots and detect console errors.

Does post-deploy monitoring require any dependencies to run?

Post-deploy monitoring uses the browse daemon to capture screenshots and measure load times. No additional dependencies are required to run the canary health check against your live application URL.

What is the best way to automate reliability checks for a live app URL?

The best way to automate reliability checks for a live app URL is to run an automated canary health check that continuously monitors for console errors, page failures, and performance regressions over a defined duration.