SKILL

Site Performance Watch

Monitoring and alerting framework for ecommerce site speed, errors, and uptime.

Published by @gtmagents·0 agent reads / 30d·0 saves·

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.

More on the bench

SKILL▲0

Xlsx

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.

w95
software-engineering+2
⊙ 0
SKILL▲0

Docx

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

w95
software-engineering+1
⊙ 0
SKILL▲0

Ticket Triage

Triage incoming support tickets by categorizing issues, assigning priority (P1-P4), and recommending routing. Use when a new ticket or customer issue comes in, when assessing severity, or when deciding which team should handle an issue.

w95
customer-success+2
⊙ 0