/inbox-exploration

name: inbox-exploration
description: >
  Explore PostHog's Inbox and act on what it surfaces — the place where signal reports cluster into
  actionable issues and trends. Use when the user asks "what's in my inbox?", "what should I look at?",
  "which reports are actionable?", "what's PostHog flagged recently?", asks about a specific report by
  ID or title, wants to act on / fix / implement a report (turn it into a PR), wants to resolve,
  dismiss, or snooze a report, or wants to see which signal sources are configured. Covers listing, filtering,
  drilling into, and acting on reports, plus pointers to the deeper `signals` skill when raw signals
  or semantic search are needed.

Exploring the Inbox

The **Inbox** is where PostHog surfaces signal reports — clusters of related observations (signals) that have been aggregated into a single issue or trend (e.g. "Error rate spiked 3× on /checkout"). Reports come from multiple source products: error tracking, session replay, web analytics, experiments, and integrations like Linear, GitHub, and Zendesk.

Inbox is part of [PostHog Desktop](https://posthog.com/desktop), PostHog's agentic surface for engineering teams.

Don't assume the user's project has reports, or that any signal sources are configured — plenty of projects don't have Inbox set up. Always run the setup-check workflow below before answering the user's actual question.

When to use this skill

• "What's in my inbox?" / "What should I look at first?"
• "Show me actionable reports" / "What's PostHog flagged recently?"
• "Are there any reports about <topic / product area>?"
• "What signal sources are configured for this project?"
• The user pastes a report ID or URL and wants context
• "Fix this inbox item" / "turn this report into a PR" / "implement this report" — see

_Workflow: act on an actionable report_

• "Dismiss this" / "snooze this report" / "mark this resolved" / "I've fixed this" — see

_Workflow: resolve, dismiss, or snooze a report_

For deeper investigation, hand off to other skills and tools:

• **`signals` skill** — query `document_embeddings` via HogQL for raw signal text, semantic

search across signals, or to inspect every signal that contributed to a report.

• **PostHog's product-specific MCP tools** — when a report points at a specific error, log line,

session, person, or time range, reach for the matching domain tool to pull richer context:

• Error tracking: `query-error-tracking-issues-list`, `query-error-tracking-issue`,

`query-error-tracking-issue-events` for error-tracking-sourced reports

• Logs: `query-logs`, `logs-count-ranges` to find log activity around the issue
• Session replays: `query-session-recordings-list`, `session-recording-get` to find

recordings of affected users

• Persons / activity: `persons-retrieve`, `advanced-activity-logs-list` to inspect a specific user's

behavior

• Trends / SQL: `query-trends`, `execute-sql` for ad-hoc verification queries

A signal report tells you _what_ PostHog clustered. The product-specific tools tell you the _underlying detail_ — pair them when the user wants to dig in.

Available tools

| Tool | Purpose | | ------------------------------------- | ------------------------------------------------------------------------------------------------------------- | | `inbox-reports-list` | Paginated list of reports with filters (status, search, etc.) | | `inbox-reports-retrieve` | Full detail for a single report | | `inbox-reports-claim` | Claim or release a report, and optionally attach its implementation PR | | `inbox-report-artefacts-list` | A report's full work log — `signal_finding` evidence, status judgments, commits, task runs, notes (read-only) | | `inbox-report-artefacts-retrieve` | Full detail for a single artefact (read-only) | | `inbox-reports-set-state` | Resolve (`resolved`), dismiss (`suppressed`), or snooze (`potential`) a single report | | `inbox-reports-bulk-set-state` | Same transition for 1–100 reports in one call (per-id result) | | `inbox-source-configs-list` | Configured signal sources (which products feed the inbox) | | `inbox-source-configs-retrieve` | Full record for a single source config | | `inbox-source-configs-partial-update` | Toggle a source's `enabled` flag (or adjust its `config`) | | `posthog:execute-sql` (signals skill) | HogQL access to underlying signals (read the `signals` skill first) |

The `inbox-reports-*-list` / `-retrieve`, `inbox-report-artefacts-list` / `-retrieve`, and `inbox-source-configs-*-list` / `-retrieve` tools are read-only. The exposed writes are `inbox-reports-set-state` (resolve / dismiss / snooze a single report), `inbox-reports-bulk-set-state` (the same transition for 1–100 reports in one call), `inbox-reports-claim` (claim / release / attach a PR), see _Workflow: resolve, dismiss, or snooze a report_ — and `inbox-source-configs-partial-update`, which flips a source's `enabled` flag on or off (e.g. `{enabled: false}` to stop a source feeding the inbox); `-create` / `-update` exist too for standing a source up or replacing it wholesale. Pausing processing is not exposed via MCP.

Terminology

What each report status means (in roughly the order a triage agent should care about):

• `r