About site-performance-watch
A skill for monitoring website performance during campaigns and launches, and investigating conversion declines linked to latency or availability. It covers KPI selection, segmentation, alerting, diagnostics, and incident communication.
Key features
- 01Web performance KPI framework
- 02Device and traffic segmentation
- 03Threshold and escalation rules
- 04Logging and tracing diagnostics
- 05Incident communication templates
Use cases
- 01Monitoring launches and campaigns
- 02Investigating conversion drops
- 03Sharing performance incidents with teams
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ gtmagents/ gtm-agents --skill site-performance-watchAfter installing, type/site-performance-watchin Claude Code to confirm it loaded.
Details
From the project READMESite Performance Watch Skill
When to Use
- Setting up proactive monitoring during campaigns or launches.
- Investigating conversion drops tied to latency or availability issues.
- Communicating performance incidents to merchandising and engineering teams.
Framework
- KPI Stack – FCP, LCP, CLS, TTFB, checkout API latency, error rates, uptime.
- Segmentation – device, geography, browser, promotion, traffic source.
- Alerting Rules – thresholds, aggregation windows, escalation paths, war-room triggers.
- Diagnostics – logging, tracing, screenshot/session replay hooks.
- Comms Kit – stakeholder updates, status pages, rollback plans.
Templates
- Performance scorecard with spark lines + thresholds.
- Incident log template with root cause, mitigation, and follow-up tasks.
- Escalation matrix covering engineering, DevOps, merchandising, and CX leads.
Tips
- Pair synthetic monitoring with RUM data to catch both systemic and localized issues.
- Freeze experiment/merch changes when performance breaches critical thresholds.
- Use alongside
diagnose-conversion-dropto correlate experience and performance data.
Comments
Markdown supported