canary

Monitors a production URL for silent errors, performance regressions, and page failures after deployment.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/tropeks/Vitali --skill canary-tropeks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/tropeks/Vitali/tree/main/.claude/skills/gstack-canary
Command: npx skills add https://github.com/tropeks/Vitali --skill canary-tropeks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Production deployments often mask issues during CI, leaving critical errors and performance regressions undetected until users notice. This Skill provides a safety net by monitoring a live URL after deploy, taking baselines, and surfacing actionable alerts.

Core Features & Use Cases

  • Canary baseline capture: take screenshots, log console errors, and record load times to establish a production baseline.
  • Continuous monitoring: watch defined pages for a fixed duration and alert on regressions.
  • Health reporting: generate a summary report and optional baseline updates after verifying health.

Quick Start

Invoke /canary with your production URL to start a 10-minute monitoring session and baseline capture.

Frequently Asked Questions about canary

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

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

Post-deploy canary monitoring tracks a live production URL by capturing baseline screenshots, logging console errors, and recording load times. It continuously watches defined pages for a fixed duration to detect silent errors, performance regressions, and page failures, then produces actionable alerts plus a final health summary.

What is canary baseline capture for production deploy verification?

Canary baseline capture establishes a healthy production state by taking initial screenshots, logging console errors, and recording page load times. This baseline serves as a reference point for continuous monitoring to quickly identify performance regressions or page failures after subsequent deployments.

How do I detect silent console errors and performance regressions in production?

Detect silent console errors and performance regressions by running an automated post-deploy monitoring session against live pages. This Skill uses a browse daemon to automatically capture screenshots and performance metrics, alerting you immediately if the page state degrades from the established baseline.

Can I automatically capture screenshots and health reports for specific production pages?

Yes, you can automatically capture screenshots and generate health reports for specific production pages. By invoking a monitoring session with your production URL, the browse daemon watches defined pages for a fixed duration and outputs a final health summary with optional baseline updates.

What is the best way to verify deployment health without active user traffic?

The best way to verify deployment health without active user traffic is using a canary monitoring approach that actively polls and renders the production URL. This method simulates visits via a browse daemon to capture screenshots and console errors, providing a safety net before users encounter masked deployment issues.

Do I need any external dependencies to run continuous canary monitoring?

No external dependencies are required to run continuous canary monitoring. This Skill operates independently using its built-in browse daemon to capture screenshots, console errors, and performance metrics, allowing you to establish baselines and generate health reports directly within your environment.