Official agent skill

Resolving Ingestion Warnings

by PostHog in PostHog/posthog

Diagnoses and resolves PostHog ingestion warnings — problems recorded while ingesting events (dropped events, rejected person merges, oversized payloads, invalid data).

OfficialCustom licenceAuto-check passed

Install Resolving Ingestion Warnings

skills CLI
$ npx skills add PostHog/posthog --skill resolving-ingestion-warnings -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install PostHog/posthog resolving-ingestion-warnings --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/products/ingestion/skills/resolving-ingestion-warnings .claude/skills/resolving-ingestion-warnings && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
resolving-ingestion-warnings
GitHub stars
40k
Token cost
~7k tokens
SKILL.md length
1,796 words
Files
17 (incl. references)
Skills in repo
252
Repo updated
First seen
Licence
Custom licence

At a glance

Diagnoses and resolves PostHog ingestion warnings — problems recorded while ingesting events (dropped events, rejected person merges, oversized payloads, invalid data).

  • Works in 5 steps: Find the warnings: call… → Triage by severity — the health issue… → Route by type using the table below.… → …
  • A user asks why events are missing
  • SKILL.md covers Workflow and Warning types and fixes
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Resolving Ingestion Warnings is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Diagnoses and resolves PostHog ingestion warnings — problems recorded while ingesting events (dropped events, rejected person merges, oversized payloads, invalid data). Use when a user asks why events are missing, dropped, or undercounted, why identify/alias calls don't work or accounts stay duplicated, why person or group properties aren't updating or profiles look inflated, why recordings have gaps, heatmaps are empty, LLM token counts are missing, why cookieless events vanish, or whenever the ingestionwarning…

Its SKILL.md is about 7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 17 other files, including reference files (for example `references/fixing-ai-endpoint-rejections.md`, `references/fixing-cannot-merge-already-identified.md` and `references/fixing-capture-replay-rejections.md`).

It works with PostHog. The repository describes itself as: :hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error…

When your agent uses it

  • A user asks why events are missing
  • Why identify/alias calls dont work
  • Accounts stay duplicated
  • Group properties arent updating

Example prompts

  • “Use the resolving-ingestion-warnings skill to diagnose and resolves PostHog ingestion warnings — problems recorded while ingesting events (dropped…”
  • “/resolving-ingestion-warnings”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Find the warnings: call posthog:health-issues-summary for the overall shape, then posthog:health-issues-list (kind=ingestion_warning…
  2. Triage by severity — the health issue severity mirrors what happened to the data
  3. Route by type using the table below. Where a references/fixing-*.md file exists, read it — it has the full diagnosis and per-SDK fixes…
  4. Pull the offending events: health issues don't carry per-event samples, so use posthog:execute-sql against system.ingestion_warnings to…
  5. Verify any fix: the ingestion_warning health issue auto-resolves once the warning stops firing, so re-run posthog:health-issues-list (or…

What it can do on your machine

Read from SKILL.md and the folder at commit 812e5c6. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Resolving Ingestion Warnings loads about 7k tokens when it runs, and up to ~25k if it reads all its reference files. Until then it costs about 226 tokens; SKILL.md has 1,796 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~226
When it runs · the whole SKILL.md, loaded when a task matches
~7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~25k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,796 words (~7,043 tokens).

“Ingestion warnings record problems PostHog hit while ingesting a project's events. They are the first place to look when events are missing, counts are lower than expected, or identify/merge calls don't behave.”

— opening of SKILL.md by PostHog, Custom licence
name
resolving-ingestion-warnings

Read the full SKILL.md on GitHub

Files

SKILL.md and 16 other files (references) in products/ingestion/skills/resolving-ingestion-warnings of PostHog/posthog.

  • SKILL.md
  • references/fixing-ai-endpoint-rejections.md
  • references/fixing-cannot-merge-already-identified.md
  • references/fixing-capture-replay-rejections.md
  • references/fixing-cookieless-warnings.md
  • references/fixing-event-dropped-by-transformation.md
  • references/fixing-event-dropped-too-old.md
  • references/fixing-group-key-too-long.md
  • references/fixing-ignored-invalid-timestamp.md
  • references/fixing-invalid-ai-token-property.md
  • references/fixing-invalid-distinct-ids.md
  • references/fixing-invalid-heatmap-data.md
  • references/fixing-merge-race-condition.md
  • references/fixing-message-size-too-large.md
  • references/fixing-person-properties-size-violation.md
  • references/fixing-process-person-profile-warnings.md
  • references/fixing-session-replay-warnings.md

Open the folder on GitHubat commit 812e5c6

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in PostHog/posthog, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Resolving Ingestion Warnings next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Resolving Ingestion Warnings compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Resolving Ingestion Warnings this skillPostHog/posthog40k—~7kAutomated safety check: PassCustom licence
Opik Analytics Instrumentationcomet-ml/opik22k—~4.4kAutomated safety check: PassApache-2.0
C15tc15t/c15t1.9k1 repos~1.6kAutomated safety check: PassApache-2.0
Define Feature Flagmacro-inc/macro4.6k—~780Automated safety check: PassAGPL-3.0
Soku CLIAbout-Intelligence/soku-cli305—~2.4kAutomated safety check: PassMIT
Compare Array Bundle SizePostHog/posthog-js628—~599Automated safety check: PassCustom licence

Similar skills

  • Shows how to add product analytics events to Opik's frontend, Java backend and Python SDK, all reporting through Segment to PostHog with an opik_ name prefix.

    22k GitHub stars~4.4k tokensUpdated today
    Data & AnalyticsAuto-check passed
  • C15t

    c15t/c15t

    Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.

    1.9k GitHub starsUsed in 1 repo~1.6k tokens
    Legal & ComplianceAuto-check passed
  • Define Feature Flag

    macro-inc/macro

    Define a frontend feature flag with defineFlag and wire its readers.

    4.6k GitHub stars~780 tokensUpdated today
    Frontend & DesignAuto-check passed
  • Soku CLI

    About-Intelligence/soku-cli

    Guides an agent through the soku command line tool for ads, GA4 and PostHog data reads, ads writes, SEO hosting, automations, files and skill management.

    305 GitHub stars~2.4k tokensUpdated today
    Marketing & SEOAuto-check passed
  • Compare Array Bundle Size

    PostHog/posthog-js

    Official

    Quickly compare the posthog-js array.js bundle size in the current working tree against a git baseline using the repository's esbuild proxy.

    628 GitHub stars~599 tokensUpdated today
    Frontend & DesignAuto-check passed
  • Telemetry Analytics

    OpenHands/OpenHands

    This skill should be used when the user asks to "add tracking", "add a PostHog event", "change telemetry consent", "instrument onboarding", "debug analytics", or changes telemetry.ts…

    90k GitHub stars~305 tokensUpdated today
    DevOps & CloudAuto-check passed

More from PostHog/posthog

All 252 skills in this repo
  • Authoring Log Alerts

    PostHog/posthog

    Official

    Author useful, low-noise log alerts on services in a PostHog project.

    40k GitHub stars~3k tokensUpdated today
    Auto-check passed
  • Official

    Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…

    40k GitHub stars~4.2k tokensUpdated today
    Auto-check passed
  • Official

    Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM).

    40k GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Exploring Apm Traces

    PostHog/posthog

    Official

    Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.

    40k GitHub stars~3.5k tokensUpdated today
    Auto-check passed
  • Exploring LLM Traces

    PostHog/posthog

    Official

    Debug and inspect LLM/AI agent traces using PostHog's MCP tools.

    40k GitHub stars~4.4k tokensUpdated today
    Auto-check passed
  • Investigate Metric

    PostHog/posthog

    Official

    Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.

    40k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

Works with

Questions about Resolving Ingestion Warnings

What does Resolving Ingestion Warnings do?

Diagnoses and resolves PostHog ingestion warnings — problems recorded while ingesting events (dropped events, rejected person merges, oversized payloads, invalid data). Resolving Ingestion Warnings is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Diagnoses and resolves PostHog ingestion warnings — problems recorded while ingesting events (dropped events, rejected person merges, oversized payloads, invalid data).

When should I use Resolving Ingestion Warnings?

Resolving Ingestion Warnings fits situations like: A user asks why events are missing; why identify/alias calls dont work; accounts stay duplicated; group properties arent updating.

How do I install Resolving Ingestion Warnings in Claude Code?

Run `npx skills add PostHog/posthog --skill resolving-ingestion-warnings -a claude-code`. Or copy the skill folder (products/ingestion/skills/resolving-ingestion-warnings in PostHog/posthog) into .claude/skills/resolving-ingestion-warnings in your project. Claude Code loads it when a task matches its description.

How do I install Resolving Ingestion Warnings in Codex?

Run `npx skills add PostHog/posthog --skill resolving-ingestion-warnings -a codex`. Or copy the skill folder (products/ingestion/skills/resolving-ingestion-warnings in PostHog/posthog) into .agents/skills/resolving-ingestion-warnings in your project. Codex loads it when a task matches its description.

Can I use Resolving Ingestion Warnings in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PostHog/posthog --skill resolving-ingestion-warnings -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/resolving-ingestion-warnings, .gemini/skills/resolving-ingestion-warnings, .github/skills/resolving-ingestion-warnings and .opencode/skills/resolving-ingestion-warnings in your project.

What does Resolving Ingestion Warnings need to run?

SKILL.md names no scripts, command-line tools or credentials: Resolving Ingestion Warnings is instructions for the agent only.

Does Resolving Ingestion Warnings access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Resolving Ingestion Warnings safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Resolving Ingestion Warnings use?

Resolving Ingestion Warnings has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Resolving Ingestion Warnings use?

About 7k tokens (SKILL.md is roughly 28k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 18k tokens, read only when the agent opens those files.

What are the alternatives to Resolving Ingestion Warnings?

Skills that share tags, products or a category with Resolving Ingestion Warnings: Opik Analytics Instrumentation (comet-ml/opik, 22k stars), C15t (c15t/c15t, 1.9k stars), Define Feature Flag (macro-inc/macro, 4.6k stars) and Soku CLI (About-Intelligence/soku-cli, 305 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Resolving Ingestion Warnings?

PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,200 GitHub stars. The repository holds 252 skills in this directory. The repository was last updated on October 9, 2026.

Source: PostHog/posthog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.