analytics-pipeline
A high-performance analytics pipeline for tracking events without database bottlenecks.
Install
mkdir -p .claude/skills/analytics-pipeline && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2811" && unzip -o skill.zip -d .claude/skills/analytics-pipeline && rm skill.zipInstalls to .claude/skills/analytics-pipeline
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Real-time analytics with Redis counters, periodic PostgreSQL flush, and time-series aggregation. High-performance event tracking without database bottlenecks.Key capabilities
- →Track events using Redis counters
- →Batch flush data to PostgreSQL
- →Aggregate time-series metrics
- →Perform atomic get-and-delete operations
- →Set TTL on analytics keys
How it works
Events are incremented in Redis for high-speed throughput, then a periodic worker batches these counts and performs an upsert into PostgreSQL to ensure persistence.
Inputs & outputs
When to use analytics-pipeline
- →Tracking application usage events
- →Aggregating performance metrics
- →Logging real-time interactions
About analytics-pipeline
Tracks events in real-time using Redis counters and aggregates them into PostgreSQL. This design prevents database congestion and ensures efficient time-series reporting.
Real-time analytics with Redis counters, periodic PostgreSQL flush, and time-series aggregation. High-performance event tracking without database bottlenecks.
When not to use it
- →Low-volume event tracking
- →Environments without Redis or PostgreSQL
Prerequisites
Limitations
- →Flush interval introduces latency in reporting
- →Requires Redis and PostgreSQL synchronization
How it compares
It decouples event ingestion from database writes, preventing performance bottlenecks common in direct-to-database logging.
Compared to similar skills
analytics-pipeline side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| analytics-pipeline (this skill) | 1 | 6mo | No flags | Intermediate |
| token-data-sources | 0 | 5mo | No flags | Intermediate |
| databuddy | 1 | 3mo | Caution | Intermediate |
| prisma-connection-pool-exhaustion | 1 | 6mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by dadbodgeoff
View all by dadbodgeoff →You might also like
token-data-sources
justinchuby
When debugging why the analysis page shows missing or zero token data, or when adding new cost/usage visualizations.
databuddy
databuddy-analytics
Integrate Databuddy analytics into applications using the SDK or REST API. Use when implementing analytics tracking, feature flags, custom events, Web Vitals, error tracking, LLM observability, or querying analytics data programmatically.
prisma-connection-pool-exhaustion
blader
Fix Prisma "Too many connections" and connection pool exhaustion errors in serverless environments (Vercel, AWS Lambda, Netlify). Use when: (1) Error "P2024: Timed out fetching a new connection from the pool", (2) PostgreSQL "too many connections for role", (3) Database works locally but fails in production serverless, (4) Intermittent database timeouts under load.
langfuse-cost-tuning
jeremylongshore
Monitor and optimize LLM costs using Langfuse analytics and dashboards. Use when tracking LLM spending, identifying cost anomalies, or implementing cost controls for AI applications. Trigger with phrases like "langfuse costs", "LLM spending", "track AI costs", "langfuse token usage", "optimize LLM budget".
logging-best-practices
neondatabase
Logging best practices focused on wide events (canonical log lines) for powerful debugging and analytics
alwib-backend
Tsuev
Develop and maintain the Alwib NestJS backend in `backend/`. Use when implementing or refactoring modules, controllers, services, DTO validation, Swagger docs, authentication/authorization flows, Prisma schema and migrations, and backend lint/test flows.