Canary Watch
Post-deploy monitoring for a URL: HTTP status, console errors, performance regressions, API health, static assets, and SSE streams.
- What
- Post-deploy monitoring for a URL: HTTP status, console errors, performance regressions, API health, static assets, and SSE streams.
- Cost
- Free
- Needs
- Use "Canary Watch" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a monitoring skill for verifying a deployed URL after releases, risky merges, or dependency upgrades. It watches eight signals: HTTP status, new console errors, network failures, performance regressions (LCP, CLS, INP against baseline), content integrity (did key elements like h1, nav, footer, or CTA disappear?), API health within SLA, static asset responses, and SSE stream connectivity. Three modes: a quick single-pass check, a sustained watch on an interval for a launch window, and a diff mode comparing staging against production. Alert thresholds separate critical (page not returning 200, new console errors, 5xx APIs, broken SSE) from warnings (LCP drift over 500ms, CLS over 0.1) and info-level noise, with desktop or Slack/Discord webhook notifications on critical. It pairs with CI pipelines and post-push hooks. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: a monitoring workflow, not a hosted service; the agent needs browser or HTTP tooling to run the checks, and sustained watches run until stopped or the window expires. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Canary Watch" with your Muse. Prerequisites: a deployed URL to monitor, and an agent with browser or HTTP tooling to run the checks. Monitoring workflow, not a hosted service. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/canary-watch/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Canary-watch https://myapp.com after this deploy; report HTTP status, console errors, and LCP vs baseline." 3. For launch windows, ask: "Run a sustained watch on https://myapp.com every 5 minutes for 2 hours and alert me on anything critical." Tip: run a baseline pass before the deploy so regressions are measured against something real. Safety: a skill is plain-text instructions; it runs nothing by itself. Point it only at URLs you own or are allowed to probe, and review anything Muse proposes before it touches your infrastructure.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.