skills.rest
PostHog
PostHogOFFICIAL
Explore all skills by this author →
Website𝕏@PostHogGitHub

inbox-exploration

Triage, filter, and act on PostHog Inbox signal reports via MCP tools.

713|118|Updated Aug 11, 2020
Search Tags:#triage#issue resolution#error tracking#PostHog#InBox#MCP Tools#signal reports
One-click install
npx skills add https://github.com/PostHog/posthog-foss --skill inbox-exploration
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: inbox-exploration
Source: https://github.com/PostHog/posthog-foss/tree/main/products/signals/skills/inbox-exploration
Command: npx skills add https://github.com/PostHog/posthog-foss --skill inbox-exploration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PostHog's Inbox clusters raw product signals (errors, rage clicks, session replays, integration events) into actionable reports, but knowing which reports matter, whether they are trustworthy, and how to act on them requires a structured triage workflow. This Skill guides an AI agent through listing, filtering, drilling into, resolving, and implementing fixes for Inbox reports without assuming the inbox is even configured.

Core Features & Use Cases

  • Inbox triage and prioritization: List reports filtered by status, priority, source product, or keyword, leading with reports where the current user is a suggested reviewer based on GitHub commit authorship.
  • Report lifecycle management: Resolve, dismiss, or snooze reports individually or in bulk (1-100) with canonical dismissal reasons and notes that steer future scout behavior.
  • Verified report implementation: Turn an actionable report into a PR by first validating the LLM-generated diagnosis against the actual codebase, then linking the PR back to the report.
  • Source configuration review: Inspect which signal sources (error tracking, session replay, GitHub, Linear, Zendesk) feed the inbox and toggle them on or off.
  • Use Case: A user asks "what should I look at first?" The agent checks source configs, lists ready reports, groups them by suggested-reviewer status and priority with deep links, then offers to drill into the top item and verify its diagnosis before opening a fix PR.

Quick Start

Ask the agent to show what is currently actionable in your PostHog inbox and summarize the top reports by priority.

Frequently Asked Questions about inbox-exploration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I see what is actionable in my PostHog inbox?▼

Call inbox-reports-list with status set to ready, in_progress, and pending_input to get the triage queue. Results are ordered with your suggested-reviewer reports first, then by status and recency, and each report includes a _posthogUrl deep link.

How do I resolve or dismiss a PostHog inbox report?▼

Use inbox-reports-set-state with the report ID and a state of resolved, suppressed, or potential, plus a canonical dismissal_reason and note. For multiple reports, inbox-reports-bulk-set-state applies the same transition to 1-100 IDs with per-id results.

Why is my PostHog inbox empty?▼

An empty inbox usually means no signal sources are configured, all sources are disabled, or signals have not clustered into reports yet. Check inbox-source-configs-list first; if no configs exist, install PostHog Desktop to start receiving signals.

Can I turn an inbox report into a pull request automatically?▼

Yes, but verify the report's diagnosis against the actual code first, since summaries are LLM-generated and can be stale or wrong. Open the PR referencing the report's URL; the report resolves automatically when the PR merges.

What does is_suggested_reviewer mean on an inbox report?▼

It means the current PostHog user is among up to three people flagged as best-placed to act on the report, based on GitHub commit authorship of the relevant code mapped to linked PostHog identities. It is a heuristic, not an assignment.

When should I use the signals skill instead of inbox tools?▼

Use the signals skill when you need raw signal text, semantic search across signals, or every signal behind a report via HogQL on document_embeddings. Inbox tools only expose the curated, judged report layer.

Related Skills

Explore More Software Engineering Skills→
EthGlobalBangkokEthGlobalBangkok
1

integration-nextjs-app-router

Integrate PostHog analytics into Next.js App Router with client and server instrumentation.

Official
Intermediate
CERTCCCERTCC
21

pr-comprehensive-fix

Inventory review comments and CI failures, fix them, and run targeted tests.

Official
Advanced
PostHogPostHog
58

signals

Retrieve deduplicated signals via embedding-based HogQL queries against document_embeddings.

Official
Advanced
rahlplxrahlplx

Production Monitoring

Configure Sentry, Plausible, and uptime monitoring for live Astro sites.

Community
Intermediate