canary

Monitor live apps for console errors and performance regressions after deployment.

2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/az9713/paperclip-gstack-company --skill canary-az9713
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/az9713/paperclip-gstack-company/tree/main/gstack/canary
Command: npx skills add https://github.com/az9713/paperclip-gstack-company --skill canary-az9713

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Read, Write, Glob, AskUserQuestion, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill identifies console errors, performance regressions, and page failures in a live app after deployment, ensuring that production issues are caught within the first 10 minutes.

Core Features & Use Cases

  • Post-Deploy Monitoring: Identifies console errors, performance regressions, and page failures after deploying a live app.
  • Baseline Comparison: Takes periodic screenshots and compares them against pre-deploy baselines to detect anomalies.
  • Alerting: Alerts on detected anomalies, allowing for quick resolution.
  • Use Case: Use /canary <url> to monitor a URL for 10 minutes after deploying a new version of your app.

Quick Start

To monitor a URL after deployment, type /canary <url>.

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 for errors after deployment?

Post-deploy monitoring uses periodic screenshots and a browse daemon to detect console errors, performance regressions, and page failures in a live app by comparing current state against pre-deploy baselines.

How do I detect performance regressions in a live web application?

Detect performance regressions by comparing periodic screenshots of live pages against pre-deploy baselines to identify visual anomalies, console errors, and page failures automatically.

Can I specify custom monitoring duration for post-deploy checks?

Yes, post-deploy monitoring allows custom monitoring duration and specifying pages to check, alongside a quick health check option to verify live app stability after deployment.

Does post-deploy monitoring work with pre-deploy baseline screenshots?

Yes, baseline comparison works by taking periodic screenshots of the live app post-deploy and comparing them against pre-deploy baselines to detect anomalies, console errors, and page failures.

What is the best way to catch production issues immediately after a release?

Run post-deploy monitoring on a live URL for 10 minutes to catch production issues early by detecting console errors, performance regressions, and page failures against pre-deploy baselines.

When should I not use a 10-minute post-deploy monitoring window?

A 10-minute post-deploy monitoring window may not detect slow-burning memory leaks or background job failures that only manifest under sustained traffic loads over extended periods.