diagnosing-failed-warehouse-syncs作者： posthog
Work top-down when a data warehouse source or table is failing, stuck, or producing bad data: source → schema → recovery action. Do not jump straight to "resync from scratch" — that discards synced data and restarts from zero, which is rarely the right first step.
npx skills add https://github.com/posthog/posthog --skill diagnosing-failed-warehouse-syncs來自 posthog 的更多技能
error-tracking-go
by posthog
PostHog error tracking for Go
integration-laravel
by posthog
PostHog integration for Laravel applications
integration-nextjs-app-router
by posthog
PostHog integration for Next.js App Router applications
logs-other
by posthog
PostHog logs for Other Languages
logs-python
by posthog
PostHog logs for Python
analyzing-experiment-session-replays
by posthog
Analyze session replay patterns across experiment variants to understand user behavior differences. Use when the user wants to see how users interact with…
auditing-experiments-flags
by posthog
Audit PostHog experiments and feature flags for configuration issues, staleness, and best-practice violations. Read when the user asks to audit, health-check,…
auditing-warehouse-data-health
by posthog
This skill produces a project-wide audit of the data warehouse pipeline. Use it when the user wants a summary of everything broken , not a deep-dive on one sync. The deep-dive on individual failures is diagnosing-failed-warehouse-syncs ; this skill is the scan that tells them where to look first.