analytics-audit

Detect analytics SDKs, inventory tracked events, and verify funnel coverage.

489|254|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/me2resh/apexyard --skill analytics-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analytics-audit
Source: https://github.com/me2resh/apexyard/tree/main/marketplace/audit-pack/.claude/skills/analytics-audit
Command: npx skills add https://github.com/me2resh/apexyard --skill analytics-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Poor or inconsistent analytics tracking makes it impossible to measure onboarding, activation, and conversion accurately, blocking reliable product decisions.

Core Features & Use Cases

  • SDK detection & configuration review: Identifies which analytics SDK is initialized (e.g., GA4, Mixpanel, PostHog, Segment, or custom) and where it’s configured.
  • Event inventory & naming consistency checks: Enumerates tracked events across the codebase, captures key properties, and flags inconsistent naming conventions.
  • Funnel completeness verification: Checks whether core funnel steps (signup, activation, purchase if applicable, retention) are instrumented end-to-end.

Use case: run the audit when launch-check shows analytics WARN/FAIL to pinpoint missing events (like a missing signup_complete) and missing dashboard/config documentation.

Quick Start

Run /analytics-audit with your project path to generate an analytics audit report covering SDK setup, event taxonomy, funnel completeness, and dashboard readiness.

Frequently Asked Questions about analytics-audit

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

FAQPage Schema
How do I check if analytics event tracking is properly configured for a product launch?

Funnel coverage verification checks whether core funnel steps like signup, activation, purchase, and retention are instrumented end-to-end. It scans tracking call patterns to ensure no steps are missing, producing a findings table with severity scoring for incomplete sequences.

Does the analytics audit detect specific SDKs like GA4, Mixpanel, or Segment?

Event naming consistency checks enumerate tracked events across the codebase, capture key properties, and flag inconsistent naming conventions. This ensures your event taxonomy remains uniform and reliable for accurate product decision-making.

When should I run an analytics instrumentation audit?

Run an analytics instrumentation audit during product launch readiness checks or ongoing QA workflows whenever analytics status shows WARN or FAIL. It pinpoints missing events and missing dashboard or configuration documentation that block reliable measurement.

What is the best way to inventory tracked events and evaluate funnel coverage?

Running an analytics audit with your project path generates a report covering SDK setup, event taxonomy, funnel completeness, and dashboard readiness. It resolves project naming and persists the run via the shared audit-history library.