check-analytics
por jeftekhari
Data & AnalyticsResumen
Audit existing Google Analytics implementation.
Descripción
Qué hace esta skill
Audits an existing Google Analytics implementation by scanning the codebase for tracking code, measurement IDs, and configuration issues. Produces a structured report categorizing problems by severity and listing missing event coverage.
Running this against the codebase surfaces configuration issues and missing events in one pass instead of manually grepping and cross-referencing GA4 documentation.
Cuándo usarla
- Catching deprecated Universal Analytics properties before they stop working
- Finding hardcoded GA4 measurement IDs that should be in env vars
- Auditing a new codebase before launch to check analytics completeness
- Identifying missing conversion or sign-up events in an SPA
- Reviewing consent mode compliance before a privacy audit
Flujo de trabajo de ejemplo
User asks: audit the analytics setup in this Next.js project
- 1
Search codebase for gtag, dataLayer, GTM-, UA-, and G- identifiers
- 2
Detect implementation method (gtag.js, GTM container, npm package)
- 3
Check for deprecated UA properties, missing pageview tracking, hardcoded IDs, and debug mode in production
- 4
Analyze custom events and compare against expected conversion events
- 5
Compile findings into a prioritized report with Critical, Warning, and Suggestion categories
Markdown audit report listing detected provider and measurement IDs, ranked issues, and an event coverage table with next steps
Instalación
clawhub install jeftekhari/check-analyticsEjecuta el comando de la CLI o pega el prompt en Claude Code, Cursor, Codex o el agente de programación que uses.