skills.rest
AAbdulghany
AAbdulghanyCOMMUNITY
Explore all skills by this author →
𝕏@AAbdulghanyyGitHub

analytics-audit

Scan codebases for analytics SDKs, events, funnels, and dashboards.

Updated Apr 15, 2026
Search Tags:#analytics#audit#dashboard#tracking#funnel#event-naming
One-click install
npx skills add https://github.com/AAbdulghany/fms --skill analytics-audit-aabdulghany
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analytics-audit
Source: https://github.com/AAbdulghany/fms/tree/main/.claude/skills/analytics-audit
Command: npx skills add https://github.com/AAbdulghany/fms --skill analytics-audit-aabdulghany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill performs a deep-dive into analytics instrumentation to ensure tracking is properly configured, events follow a consistent naming scheme, and key funnels and dashboards exist, enabling reliable data-driven decisions.

Core Features & Use Cases

  • SDK detection and verification across the codebase to confirm analytics libraries are initialized correctly.
  • Event inventory and naming consistency check to ensure all tracked events align with conventions.
  • Funnel coverage assessment to validate essential user journeys are instrumented.
  • Dashboard and reporting presence verification to ensure accessible, actionable insights.
  • Privacy and compliance checks to flag potential PII exposure in event properties.

Quick Start

Run the analytics-audit against your frontend and backend codebase to generate a findings report.

Frequently Asked Questions about analytics-audit

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

FAQPage Schema
How do I audit analytics tracking across my codebase?▼

To audit analytics tracking, scan your frontend and backend codebases for SDK initializations, enumerate tracked events, verify funnel steps, and generate a structured findings report to validate proper configuration.

How do I check event naming consistency for product analytics?▼

Checking event naming consistency involves inventorying all tracked events across your codebase and verifying they align with established conventions to ensure reliable data collection for product insights.

Can I verify funnel instrumentation for both frontend and backend code?▼

Yes, you can verify funnel instrumentation by scanning both frontend and backend codebases to validate that essential user journeys are properly tracked for A/B testing and monitoring.

What is the best way to detect PII exposure in analytics event properties?▼

Detecting PII exposure in analytics event properties requires privacy and compliance checks that scan event payloads across the codebase to flag potential sensitive data being sent to tracking platforms.

Does this analytics audit check for dashboard and reporting presence?▼

Yes, the analytics audit includes dashboard and reporting presence verification to ensure that accessible, actionable insights are available for the events and funnels instrumented in your codebase.

Why do my A/B testing results seem unreliable despite having tracking implemented?▼

Unreliable A/B testing results often occur when analytics instrumentation is improperly configured, funnels have missing steps, or SDKs are initialized incorrectly, which a thorough codebase audit can identify and resolve.

Related Skills

Explore More Data & Analytics Skills→
MacPhobosMacPhobos

Tauri Advanced Event System

Explain advanced event system patterns for Tauri applications.

Community
Advanced
robotijnrobotijn
3

posthog-analytics

Instrument PostHog analytics for SaaS with event naming and privacy compliance.

Community
Advanced
TeiNamTeiNam
12

laravel-verification

Automate Laravel project verification for CI/CD pipelines.

Community
Advanced
stratagastrataga

analytics-tracking

Set up GA4 and GTM analytics tracking with events, properties, and UTMs.

Community
Intermediate