canary

Monitor live URLs for console errors, performance regressions, and page failures.

1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/geoffreywoo/clawfable --skill canary-geoffreywoo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/geoffreywoo/clawfable/tree/main/.claude/skills/gstack/canary
Command: npx skills add https://github.com/geoffreywoo/clawfable --skill canary-geoffreywoo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-deploy reliability is hard to catch before users see it. This Skill watches a live URL after deployment to detect console errors, performance regressions, and page failures so you can respond quickly.

Core Features & Use Cases

  • Real-time monitoring of production pages with a browse daemon to capture screenshots, console errors, and performance metrics.
  • Optional baseline capture before deployment to establish references and detect regressions.
  • Configurable page sets and duration for continuous health checks.

Quick Start

Monitor a deployed URL for the configured duration and report baseline, screenshots, and alerts.

Frequently Asked Questions about canary

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

FAQPage Schema
How do I monitor a live URL for console errors after a production deployment?

Post-deploy monitoring of a live URL uses a browse daemon to continuously check pages, capturing screenshots, console errors, and performance metrics over a configured duration to detect production regressions.

What is a baseline capture and when do I need it for production monitoring?

Baseline capture records reference page behavior before deployment. You need it to detect performance regressions by comparing post-deploy monitoring data against pre-deploy reference metrics.

Can I target specific pages and set a custom duration for continuous health checks?

Yes, you can configure targeted page sets and set a custom duration for continuous health checks using CLI flags. This focuses the browse daemon on specific production URLs for a defined time window.

Do I need a specific environment to store canary artifacts and reports?

You need a configured environment with the ability to store canary artifacts in the .gstack/canary-reports directory. This setup stores the screenshots, baseline data, and alert outputs generated during monitoring.

What's the best way to detect performance regressions in production after a release?

To detect performance regressions after a release, capture a pre-deploy baseline, then run a post-deploy browse daemon to compare live performance metrics against that reference over a defined duration.

Why are my post-deploy page failures not being caught before users see them?

Post-deploy page failures often go unnoticed without automated monitoring. Implementing a browse daemon to continuously check for console errors and page failures over a defined duration catches these issues before broader user impact.