Umami is a self-hosted, open-source web analytics platform that serves as a privacy-focused alternative to Google Analytics. The system tracks pageviews, sessions, events, funnels, journeys, retention, attribution, revenue, and performance metrics (Core Web Vitals) through a dual-database architecture using PostgreSQL (via Prisma ORM) and ClickHouse for analytics queries. It provides real-time dashboards, session replay, heatmaps, and a customizable board/dashboard system with shareable views. The application is built with Next.js (App Router) and React, using TypeScript throughout. It features a comprehensive REST API with auto-generated OpenAPI contracts, a generated TypeScript API client package, and an MCP (Model Context Protocol) server for AI/LLM integration. Authentication supports API keys, JWT, two-factor authentication (TOTP with backup codes), and team-based multi-tenancy with role-based permissions. Key architectural patterns include a dual-database query dispatcher (`runQuery`) that selects between Prisma and ClickHouse implementations for every analytics query, a centralized request parsing and validation layer using Zod schemas, and a hook-based React data layer with TanStack Query for caching and invalidation. The codebase also includes comprehensive test coverage with Vitest unit tests, Playwright API tests, and E2E tests, plus a coverage oracle that enforces every API endpoint is documented in the OpenAPI spec.
This repository is a curated skill library for data analysis workflows, designed to be consumed by AI agents (Claude Code, Codex). It contains 31 skills organized into 6 categories: data quality validation, documentation/knowledge management, data analysis/investigation, data storytelling/visualization, stakeholder communication, and workflow optimization. Each skill is defined by a SKILL.md file with YAML frontmatter, a step-by-step process, required inputs/outputs, and optional scripts, reference materials, and asset templates. The scripts are standalone Python CLIs that generate synthetic data for demo purposes and can be adapted to real datasets. The repo is not a deployable application or a data pipeline; it is a structured knowledge base and toolset for performing data analysis tasks programmatically. It covers common analytical patterns such as null counting, duplicate detection, cohort retention, funnel conversion, A/B testing, time series anomaly detection, metric calculation, and more. The codebase is well-organized and follows consistent conventions, but shows signs of staleness (future dates in README and LICENSE, no recent activity). Dependencies are not pinned, and no environment definitions are provided, limiting reproducibility without manual setup.