check-analytics

What This Skill Does

The check-analytics skill is a comprehensive diagnostic tool designed for developers and data analysts to automate the audit of Google Analytics (GA4) and Google Tag Manager (GTM) implementations within a codebase. It proactively scans for legacy Universal Analytics (UA) tags, missing TypeScript definitions, hardcoded configuration keys, and common performance anti-patterns like blocking scripts or missing consent mode configurations. By running this skill, users receive a structured, prioritized report that categorizes findings into critical blockers, best-practice warnings, and optimization suggestions, along with a detailed matrix of event coverage.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/jeftekhari/check-analytics Ensure you have the necessary permissions to read your project's repository files as the agent needs to parse source code, environment variables, and config files to generate an accurate report.

Use Cases

• Pre-launch Audits: Before deploying a new marketing campaign, verify that all conversion tracking and event logging are functioning correctly.
• Migration Projects: Ensure that all legacy Universal Analytics tags have been successfully purged and replaced with modern GA4 tracking methods.
• Technical Debt Cleanup: Identify hardcoded IDs that should be moved into .env files to improve security and environment management.
• Compliance Checks: Verify the presence of consent mode logic to ensure your site adheres to GDPR/CCPA requirements.

Example Prompts

1. "Check the current analytics setup in this repository and tell me if I have any deprecated UA properties still lurking."
2. "Audit our GA4 implementation. I'm worried our SPA pageviews aren't firing correctly on route changes. Can you check our implementation method?"
3. "Run an analytics audit and provide a report on missing event coverage, specifically focusing on our checkout flow and form submissions."

Tips & Limitations

• Context is Key: For the most accurate results, ensure the agent has access to your package.json and any custom analytics wrapper components.
• Security: The skill automatically redacts sensitive Measurement IDs, but avoid sharing reports containing full tracking IDs in public channels.
• Limitations: This skill audits the static implementation in the code. It cannot perform a live runtime crawl to verify if pixels are firing correctly in a browser; for that, consider pairing this with browser-automation skills. Always review the output for false positives in custom naming conventions.