canary

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

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/FxHollow/100000mrr-landing --skill canary-fxhollow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/FxHollow/100000mrr-landing/tree/main/.agents/skills/gstack/canary
Command: npx skills add https://github.com/FxHollow/100000mrr-landing --skill canary-fxhollow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canary-based post-deploy monitoring helps catch console errors, performance regressions, and page failures in production before users notice.

Core Features & Use Cases

  • Watches the live app after deployment to detect issues and surface anomalies
  • Captures screenshots, compares against pre-deploy baselines, and triggers alerts
  • Supports guided telemetry and quick-start prompts to integrate into existing workflows

Quick Start

Start monitoring a URL after deploy by invoking the canary skill with a target URL and optional flags to control duration and pages.

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 app URL for issues after deployment?▼

Post-deploy monitoring detects console errors, performance regressions, and page failures by watching a live app URL, capturing baselines, taking screenshots, and alerting on anomalies after deployment.

What is canary-based post-deploy monitoring and how does it work?▼

Canary-based post-deploy monitoring works by comparing post-deploy screenshots and telemetry against pre-deploy baselines to surface production anomalies before users notice them.

How do I set up production monitoring to catch console errors after a release?▼

You set up production monitoring by invoking the skill with a target URL and optional flags to control duration and pages, using the included browser daemon to run baseline captures and compare results.

Do I need a browser daemon to capture baselines and detect page failures?▼

Yes, the included browser daemon and preconfigured skill tooling are required to run baseline captures, compare results, and trigger alerts for post-deploy verification across selected pages.

What's the best way to detect performance regressions in production after deploying?▼

Detect production performance regressions by applying post-deploy verification across the live app, capturing baselines before deployment, and comparing live results to alert on detected anomalies.

Can I control which pages and how long the post-deploy monitoring runs?▼

Yes, you can control monitoring duration and selected pages by passing optional flags when invoking the skill with a target URL to guide telemetry across the live app.