Skip to main content
skill CX Codex

auditing-warehouse-view-health — Claude Code skill: PostHog view audit

auditing-warehouse-view-health runs a project-wide check on PostHog materialized views: lists the ones that failed to refresh and points at materialized views nobody queries.

no license 204 installs ★ 101 updated 2026-10-24

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add PostHog/ai-plugin --skill auditing-warehouse-view-health -a claude-code
Open on GitHub

What auditing-warehouse-view-health does

Point the skill at a PostHog project and it pulls the warehouse data-health endpoint, keeping only entries of type materialized_view. Each failure comes back as a short line: view name, error text, when it broke, plus a link. Nothing broken means the answer is that views are fine, and the skill stops there instead of padding the report.

Most causes sit inside the view definition. A typo in HogQL, a table that no longer exists, a type mismatch. Ask for the trail and it reads view-run-history for that one view. One exception: an error starting with Not published: comes from failed data-quality checks rather than the query, so it belongs to debugging-failed-data-quality-checks.

A wider sweep is opt-in. With warehouse-suggestions-list and view-list the skill surfaces views marked materialized that nobody reads, which keep refreshing and keep costing compute. Nothing changes during the audit itself: unmaterializing through view-unmaterialize or editing a query waits for your explicit go-ahead.

What it helps with

  • list every materialized view that failed to refresh
  • trace why one view keeps erroring
  • find materialized views with no readers still burning compute
  • recheck view health after a schema or HogQL edit
  • explain a dashboard that errors because its view is stale

Example prompts for the agent

  • Which materialized views are broken right now?
  • Why does monthly_revenue keep failing? Run the audit.
  • Any views that nobody reads and still cost us compute?

How to install auditing-warehouse-view-health

1Skills CLI (Vercel)

npx skills add PostHog/ai-plugin --skill auditing-warehouse-view-health -a claude-code

2Manually: put the files in place

~/.claude/skills/auditing-warehouse-view-health/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/auditing-warehouse-view-health/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about auditing-warehouse-view-health

How do I install auditing-warehouse-view-health in Claude Code?

Run npx skills add PostHog/ai-plugin --skill auditing-warehouse-view-health -a claude-code. The skill file lands at ~/.claude/skills/auditing-warehouse-view-health/SKILL.md.

What does auditing-warehouse-view-health do?

It audits materialized views across a PostHog project and reports what is failing, with the error and the failure time. On a broader request it also flags views that are materialized but unread.

How does it differ from auditing-warehouse-source-health?

That skill covers sources and syncs; this one covers materialized views. Both sit on the same data-health endpoint, but the problem types and the follow-up steps differ.

Similar skills

All skills for Data and databases →

From the same set82

The whole set →
investigating-metric-anomalies investigating-metric-anomalies turns a PostHog Metrics symptom (rising lag, error spike, falling throughput) into a probable cause backed by logs and traces. CX Codex +1 206installs choosing-trend-or-slope-view choosing-trend-or-slope-view — a skill that settles what “change over time” means before a chart gets built: the full trend interval by interval, or only the gap between the two ends. CX Codex +1 204installs auditing-warehouse-source-health auditing-warehouse-source-health audits PostHog data warehouse sources and syncs to pinpoint broken connectors, failed schemas, and degraded webhooks. CX Codex +1 204installs signals-scout-product-analytics signals-scout-product-analytics — a skill for Claude Code and Codex monitoring core product analytics flows in PostHog. Detects derived-rate regressions across funnels and retention while entrant volume holds steady. CX Codex +1 204installs building-workflows building-workflows is a Claude Code skill for building, patching, and testing PostHog automation graphs over MCP before publishing them in the visual editor. CX Codex +1 204installs exploring-replay-vision-observations The exploring-replay-vision-observations skill guides an agent through Replay Vision scanner results, from recurring patterns to individual session recordings. Use it to review findings and decide what to investigate next. CX Codex +1 203installs signals-scout-customer-analytics The signals-scout-customer-analytics skill tracks account-level engagement in PostHog and spots churn-risk or expansion patterns. Use it for recurring customer-health checks. CX Codex +1 203installs exploring-mcp-sessions exploring-mcp-sessions investigates PostHog MCP sessions to inspect tool call sequences, agent intent, and run failures. CX Codex +1 202installs

Project sponsors

Companies that keep this analytics open