skills.rest
no-session
no-sessionCOMMUNITY
Explore all skills by this author →
𝕏@pawan_kumar100GitHub

monitor

Monitors deployed web apps for console errors, performance regressions, and page failures using browser automation.

107|7|Updated Mar 29, 2026
Search Tags:#performance#monitoring#deployment#screenshots#production#regression detection#console errors
One-click install
npx skills add https://github.com/no-session/pstack --skill monitor-no-session
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: monitor
Source: https://github.com/no-session/pstack/tree/main/monitor
Command: npx skills add https://github.com/no-session/pstack --skill monitor-no-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploys that pass CI can still break in production through missing environment variables, stale CDN caches, or slow migrations. This Skill watches your live app in the first critical minutes after a deploy, catching regressions before users report them. ## Core Features & Use Cases - Baseline Capture: Take pre-deploy screenshots, console error counts, and load times per page, then compare post-deploy state against them. - Continuous Monitoring Loop: Check pages every 60 seconds for a configurable duration (1-30 minutes), alerting only on changes that persist across consecutive checks. - Severity-Based Alerts: Classify issues as CRITICAL (page load failure), HIGH (new console errors), MEDIUM (2x performance regression), or LOW (new broken links), each with screenshot evidence. - Use Case: After shipping a new dashboard page, run the monitor against your production URL for 10 minutes to confirm load times stay near baseline and no new console errors appear. ## Quick Start Monitor https://myapp.com for 10 minutes after this deploy and alert me if any page shows new console errors or slowdowns.

Frequently Asked Questions about monitor

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

FAQPage Schema
How do I monitor my website after a deployment?▼

Run the monitor against your production URL to check pages every 60 seconds for a set duration. It captures screenshots, console errors, and load times, then compares each check against a pre-deploy baseline to detect regressions.

How to detect performance regressions after a deploy?▼

Capture a baseline with load times before deploying, then monitor compares each post-deploy check against it. A page loading slower than 2x its baseline triggers a MEDIUM alert with screenshot evidence.

Can I monitor specific pages instead of the whole site?▼

Yes, pass a pages argument with a comma-separated list like /,/dashboard,/settings. Without it, the monitor auto-discovers the top internal navigation links and asks you to confirm which pages to watch.

Why does the monitor not alert on a single failed check?▼

Alerts only fire when an issue persists across two or more consecutive checks. This filters out transient network blips so you are not interrupted by false positives during monitoring.

What are the limitations of browser-based deploy monitoring?▼

It is read-only observation, not a fix tool, and it only covers the pages and duration you specify. Without a pre-deploy baseline it acts as a one-off health check rather than true regression detection.

Related Skills

Explore More Software Engineering Skills→
openclawopenclaw
9.4k

clawhub-production-release

Run and verify ClawHub production deploys and stable CLI npm releases.

Official
Intermediate
JeremiahEllingtonJeremiahEllington

investigate

Diagnose root causes of bugs through structured investigation of symptoms and code paths.

Community
Advanced
yahav123147yahav123147

qa

Run tiered QA tests on web applications and generate ship-readiness reports.

Community
Advanced
aivos-xieaivos-xie
1

self-hosted-services

Deploys/manages self-hosted Docker services like AList, Uptime Kuma, Memos for local use.

Community
Intermediate