How do I install the Posthog Inbox skill?

Run npx skillmds@latest add qingqishi/posthog-inbox in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Posthog Inbox safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Posthog Inbox?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Posthog Inbox free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Posthog Inbox?

qingqishi (@qingqishi) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Posthog Inbox by qingqishi — Agent Skill

Name: Posthog Inbox
Author: qingqishi

Posthog Inbox

Check the PostHog inbox and query PostHog data with posthog-cli. Use when the user asks to check PostHog, the inbox, signal reports, what PostHog found, or anything about PostHog analytics, error tracking, session replay, or feature flag data.

qingqishi Updated Sep 17, 2026

File contents

PostHog inbox

Use the globally installed posthog-cli (pnpm add -g @posthog/cli if missing). Do not use PostHog MCP tools, and do not run posthog-cli api skill install — this project deliberately avoids the .agents/ skill layer.

This repo's PostHog project is Qingqi.dev, ID 243843, EU cloud. Sessions inherit POSTHOG_CLI_PROJECT_ID=243843 from the env block in .claude/settings.json, which overrides the machine-level login's active project. If the variable is missing from the environment, prefix each call with it. Do not call switch-project — it changes the machine-global default for other repos.

Auth

Calls fail with Missing PostHog API key when the machine is not authenticated. Ask the user to run ! posthog-cli login (one-time, credentials stay in the home directory). Never write PostHog credentials into the repo.

Check the inbox

The inbox holds signal reports: clusters of related observations from error tracking, session replay, and other scouts.

posthog-cli api call inbox-reports-list '{"status": "ready,pending_input"}'
posthog-cli api call inbox-reports-list '{"status": "ready"}'

status takes a comma-separated list; without it the API returns every status except suppressed, mixing archived reports (resolved, failed) and in-pipeline ones (potential, candidate, in_progress) in with the actionable ones. ready is actionable now, pending_input waits on a human, earlier statuses are still in the pipeline, and suppressed (dismissed) is hidden unless include_all_statuses is true — that flag only dedupes against the whole inbox and is ignored once status is set. Filter to ready,pending_input for the live queue, or ready alone for only what can be picked up now.

Before acting on a report, read its full work log — evidence, judgments, and log entries. Reports can be stale: check already_addressed and verify the claimed gap against current code, project settings, and merged PRs before acting.

posthog-cli api call inbox-report-artefacts-list '{"report_id": "<report-uuid>"}'

Anything else PostHog

Discover tools at runtime — never guess a schema:

posthog-cli api search <topic>
posthog-cli api info <tool>
posthog-cli api call <tool> '<json>'

posthog-cli api --agent-help prints the full agent guide. Mutating tools require --confirm and explicit user direction.

---name: posthog-inboxdescription: Check the PostHog inbox and query PostHog data with posthog-cli. Use when the user asks to check PostHog, the inbox, signal reports, what PostHog found, or anything about PostHog analytics, error tracking, session replay, or feature flag data.---# PostHog inboxUse the globally installed `posthog-cli` (`pnpm add -g @posthog/cli` if missing). Do not use PostHog MCP tools, and do not run `posthog-cli api skill install` — this project deliberately avoids the `.agents/` skill layer.This repo's PostHog project is **Qingqi.dev, ID `243843`, EU cloud**. Sessions inherit `POSTHOG_CLI_PROJECT_ID=243843` from the env block in `.claude/settings.json`, which overrides the machine-level login's active project. If the variable is missing from the environment, prefix each call with it. Do not call `switch-project` — it changes the machine-global default for other repos.## AuthCalls fail with `Missing PostHog API key` when the machine is not authenticated. Ask the user to run `! posthog-cli login` (one-time, credentials stay in the home directory). Never write PostHog credentials into the repo.## Check the inboxThe inbox holds signal reports: clusters of related observations from error tracking, session replay, and other scouts.```shposthog-cli api call inbox-reports-list '{"status": "ready,pending_input"}'posthog-cli api call inbox-reports-list '{"status": "ready"}'````status` takes a comma-separated list; without it the API returns every status except `suppressed`, mixing archived reports (`resolved`, `failed`) and in-pipeline ones (`potential`, `candidate`, `in_progress`) in with the actionable ones. `ready` is actionable now, `pending_input` waits on a human, earlier statuses are still in the pipeline, and `suppressed` (dismissed) is hidden unless `include_all_statuses` is true — that flag only dedupes against the whole inbox and is ignored once `status` is set. Filter to `ready,pending_input` for the live queue, or `ready` alone for only what can be picked up now.Before acting on a report, read its full work log — evidence, judgments, and log entries. Reports can be stale: check `already_addressed` and verify the claimed gap against current code, project settings, and merged PRs before acting.```shposthog-cli api call inbox-report-artefacts-list '{"report_id": "<report-uuid>"}'```## Anything else PostHogDiscover tools at runtime — never guess a schema:```shposthog-cli api search <topic>posthog-cli api info <tool>posthog-cli api call <tool> '<json>'````posthog-cli api --agent-help` prints the full agent guide. Mutating tools require `--confirm` and explicit user direction.

Frequently asked questions