skills.rest
Nikhil-Chopra-7
Nikhil-Chopra-7COMMUNITY
Explore all skills by this author →
GitHub

analytics-qa

Verify frontend analytics events against a formal spec via intercepted network requests.

1|Updated Apr 25, 2026
Search Tags:#analytics#frontend#qa#verification#reporting#tracking#segment
One-click install
npx skills add https://github.com/Nikhil-Chopra-7/claude-frontend-skills --skill analytics-qa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analytics-qa
Source: https://github.com/Nikhil-Chopra-7/claude-frontend-skills/tree/main/analytics-qa
Command: npx skills add https://github.com/Nikhil-Chopra-7/claude-frontend-skills --skill analytics-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Analytics QA automates verification that frontend analytics events fire correctly against a defined event spec, catching missing, extra, or misnamed events before they reach production.

Core Features & Use Cases

  • Validate event names and properties against PRD or segment-events.md
  • Support page load, click, and form interactions with timing checks
  • Generate a concise QA report highlighting pass/fail per event

Quick Start

Run a quick analytics QA pass on a target page to validate the trackEventV2 events against the event spec.

Frequently Asked Questions about analytics-qa

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

FAQPage Schema
How do I verify frontend analytics events against a spec?▼

Verify frontend analytics events by intercepting network requests to Segment-like APIs and comparing fired event names and properties against a PRD-derived spec to produce a per-event pass/fail report.

Can I validate Segment tracking events for clicks and page loads automatically?▼

Yes, you can validate Segment tracking events for page loads, clicks, and user interactions automatically by capturing network requests and checking event names and properties against formal tracking specifications.

What's the best way to QA missing or misnamed analytics events before production?▼

The best way to QA missing or misnamed analytics events is automating end-to-end verification against a defined event spec, catching tracking discrepancies in page-load and interaction events before they reach production.

Do I need a proxy to intercept Segment network requests for analytics verification?▼

You can intercept Segment network requests for analytics verification either by proxying traffic or directly capturing requests to api.segment.io/segment.com, comparing the payload's event names and properties to your spec.

How does event spec verification work for frontend reporting?▼

Event spec verification for frontend reporting works by matching intercepted analytics network payloads against PRD or segment-events.md definitions, generating a concise QA report highlighting pass/fail status for each tracked event.

Does analytics event verification work with tracking systems other than Segment?▼

Yes, analytics event verification works with any Segment-like tracking system, provided you can intercept the network requests and have a formal event spec or segment-events.md file to compare event names and properties against.

Related Skills

Explore More Data & Analytics Skills→
alexfazioalexfazio
159

cc-trace

Intercept and inspect Claude Code API traffic using mitmproxy.

Community
Advanced
petrkindlmannpetrkindlmann
64

qa-metrics

Define QA metrics with formulas, targets, and CI automation hooks.

Community
Advanced
christhz666christhz666

webapp-testing

Automate Playwright testing and debugging of local web applications.

Community
Intermediate
PostHogPostHog
58

integration-astro-ssr

Integrate PostHog analytics into Astro server-rendered apps with API routes.

Official
Intermediate