Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
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.
When to use it
- 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
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: audit the analytics setup in this Next.js project
- 1Search codebase for gtag, dataLayer, GTM-, UA-, and G- identifiers
- 2Detect implementation method (gtag.js, GTM container, npm package)
- 3Check for deprecated UA properties, missing pageview tracking, hardcoded IDs, and debug mode in production
- 4Analyze custom events and compare against expected conversion events
- 5Compile 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