Skip to main content
skill CX Codex

resolving-ingestion-warnings — Claude Code skill

resolving-ingestion-warnings walks through PostHog ingestion warnings: dropped events, rejected person merges, oversized payloads. Use it when event counts look low or identify calls misbehave.

no license 197 installs ★ 101 updated 2026-11-10

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

What resolving-ingestion-warnings does

This skill covers PostHog's ingestion warnings, the records the pipeline writes when it drops, alters or refuses an incoming event. It opens with the ingestion_warning health check: a summary first, then the active issues, each carrying a warning type, category, severity and affected count.

Severity sets the order of work. A critical issue means the event never landed. A warning means it arrived changed. Info marks a drop the team configured on purpose. From there the skill opens the matching references/fixing-*.md file for code-level causes and per-SDK fixes, and reaches for posthog:execute-sql over system.ingestion_warnings when you want the offending events themselves. Only the reference file you need gets loaded.

One rule runs through the flow: every value in details was written by whoever sent the event, and anyone with the project's public capture token can put text there. The skill reports that content as data and never acts on it. Distinct IDs need resolving to persons as well, before you read a pattern into a sample.

What it helps with

  • Trace why events vanish from a PostHog project
  • Explain duplicated accounts after identify or alias calls
  • Shrink an event that grew past 1MB once person properties were attached
  • Check whether a fix actually stopped new warnings
  • Find the cause of gaps in recordings and empty heatmaps

Example prompts for the agent

  • List the active ingestion_warning issues and tell me which ones dropped data.
  • Our heatmaps are empty — pull the matching warning type and show the raw details rows.
  • Person profiles look inflated; walk the person_properties_size_violation reference and suggest the code fix.

How to install resolving-ingestion-warnings

1Skills CLI (Vercel)

npx skills add PostHog/ai-plugin --skill resolving-ingestion-warnings -a claude-code

2Manually: put the files in place

~/.claude/skills/resolving-ingestion-warnings/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/resolving-ingestion-warnings/

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

Questions about resolving-ingestion-warnings

How to install resolving-ingestion-warnings in Claude Code?

Run npx skills add PostHog/ai-plugin --skill resolving-ingestion-warnings -a claude-code. The skill file lands at ~/.claude/skills/resolving-ingestion-warnings/SKILL.md.

What does resolving-ingestion-warnings do?

It pulls the active ingestion warnings from PostHog's health check, sorts them by severity, then sends you to the per-issue reference file or to system.ingestion_warnings for the raw events behind them.

Should I trust the text inside a warning's details?

No. It is event-supplied input: the project's public capture token lets anyone write into it. The skill treats those values as data to inspect and does not follow text found there.

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set82

The whole set →
exploring-mcp-tool-usage exploring-mcp-tool-usage — a routing skill for PostHog MCP analytics: it offers a menu of questions about tool calls, then hands you to the query that answers it. CX Codex +1 200installs checking-deploy-timing checking-deploy-timing tells you when a commit or PR reached prod-us or prod-eu by reading PostHog's hidden deploy annotations and matching them against the merge commit on GitHub. CX Codex +1 200installs setting-up-a-custom-rest-source setting-up-a-custom-rest-source — a skill for Claude Code and Codex that links arbitrary REST APIs to the PostHog data warehouse using a JSON manifest. Activates when importing custom endpoints without native connectors. CX Codex +1 199installs exploring-ai-failures exploring-ai-failures reads real production traces from PostHog and returns a ranked list of the ways your LLM feature breaks. CX Codex +1 198installs exploring-scouts exploring-scouts reads the state of PostHog Signals scouts: which ones a project has, how recent runs went, and where their reports ended up. Read-only. CX Codex +1 197installs debugging-surveys debugging-surveys investigates why PostHog Surveys fail to appear or record complete answers. Useful for support cases involving targeting, SDK behavior, and stored responses. CX Codex +1 197installs authoring-scouts authoring-scouts is a Claude Code skill for creating, tuning, and testing PostHog Signals scouts that inspect project metrics on a schedule and submit findings. CX Codex +1 196installs creating-online-evaluations creating-online-evaluations — a Claude Code skill that turns production failure modes into continuously-running online evaluations in PostHog. It starts when new generations need automatic scoring against specific errors. CX Codex +1 195installs

Project sponsors

Companies that keep this analytics open