Files
gh-gtmagents-gtm-agents-plu…/skills/site-performance-watch/SKILL.md
2025-11-29 18:30:30 +08:00

32 lines
1.3 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
name: site-performance-watch
description: Monitoring and alerting framework for ecommerce site speed, errors, and
uptime.
---
# Site 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
1. **KPI Stack** FCP, LCP, CLS, TTFB, checkout API latency, error rates, uptime.
2. **Segmentation** device, geography, browser, promotion, traffic source.
3. **Alerting Rules** thresholds, aggregation windows, escalation paths, war-room triggers.
4. **Diagnostics** logging, tracing, screenshot/session replay hooks.
5. **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-drop` to correlate experience and performance data.
---