Canary

Monitors live applications for console errors, performance regressions, page failures, and screenshot anomalies after deployment.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/aporto-tech/aporto-agent-skills --skill canary-aporto-tech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Canary
Source: https://github.com/aporto-tech/aporto-agent-skills/tree/main/skills/gstack/canary
Command: npx skills add https://github.com/aporto-tech/aporto-agent-skills --skill canary-aporto-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires browser_automation, deployment_inspection, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides post-deployment monitoring for live applications, identifying console errors, performance regressions, and page failures, ensuring the stability and reliability of the deployed software.

Core Features & Use Cases

  • Error Detection: Monitors for console errors in real-time.
  • Performance Monitoring: Identifies performance regressions.
  • Page Failure Detection: Checks for page failures.
  • Screenshot Comparison: Compares periodic screenshots against pre-deploy baselines.
  • Alerting: Alerts on detected anomalies.
  • Use Case: After deploying a new version of an application, use this Skill to monitor for any issues that may have been introduced during the deployment process.

Quick Start

Run the 'gstack-canary' skill to monitor the live application for post-deployment issues.

Frequently Asked Questions about Canary

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

FAQPage Schema
How do I monitor live applications for console errors post-deployment?▼

Post-deployment monitoring detects live application console errors by utilizing browser automation to track real-time page failures and performance regressions, ensuring software stability after new releases.

What is the best way to detect performance regressions in continuous integration workflows?▼

Detecting performance regressions in continuous integration workflows requires periodic screenshot comparisons against pre-deploy baselines to identify visual anomalies and page failures during the deployment process.

Do I need browser automation to check for page failures after a release?▼

Browser automation is required to check for page failures post-release, as it enables live application inspection and captures performance regressions without manual intervention.

Can I use screenshot comparison to identify application stability issues?▼

Screenshot comparison identifies application stability issues by comparing periodic live screenshots against pre-deploy baselines to detect visual regressions and alert on anomalies.

Why does post-deployment monitoring alert on detected anomalies?▼

Post-deployment monitoring alerts on detected anomalies to immediately notify teams of console errors and page failures, allowing rapid remediation of issues introduced during the deployment process.