Investigating Replay
by PostHog469d1773e9cbNo licenseListed Oct 8, 2026Updated Oct 8, 2026
Investigates a session recording by gathering metadata, person profile, same-session events, and linked error tracking issues in one pass. Use when a user provides a recording or session ID and wants to understand what happened — who the user was, what they did, what errors occurred, and whether there are related error tracking issues. Replaces the manual chain of session-recording-get, persons-retrieve, execute-sql, and query-error-tracking-issues-list.
Only the file list is public. File contents are available once the skill is installed in a workspace.
| Path | Size | Type |
|---|---|---|
| SKILL.md | 9.5 KB | text/markdown |
Source and attribution
Source:PostHog/ai-plugininskills/investigating-replayat commit469d177
License: No license
Content belongs to its original authors. SourceWeft indexes it from a public repository.
More from PostHog/ai-plugin
Writing Simplified Technical English
PostHog
Applies ASD-STE100 simplified technical English rules to make agent-written prose unambiguous and actionable.
Working With Task Comments
PostHog
Reads and interprets comments on PostHog tasks, artifacts, and canvases through the PostHog MCP exec dispatcher.
Working With Skills
PostHog
Guides agents in using PostHog's skill-* MCP tools to discover, read, create, update, and refactor skills.
Working With Scouts
PostHog
Operating manual for delegating watching jobs to PostHog Signals scouts, acting on their reports, and steering the fleet over time.
Validating And Publishing Canvases
PostHog
Validate and publish a canvas source project safely: the source-project shape, declared capabilities, reading the current version pointer, iterating on validation diagnostics, guarded publishing with expected_current_version_id, staging a draft build and promoting it, waiting out the queued build, and recovering from a 409 version_conflict or a 429 capacity limit without overwriting concurrent work. Use whenever a canvas edit is ready to save, a draft build is wanted, a canvas publish or build returns diagnostics or a conflict, or a task needs to understand canvas version history.
Understanding Billing Usage
PostHog
Explains PostHog billing usage and spend from the customer's visible Billing MCP tools. Use when the user asks why usage or spend is high, which product or project is driving usage, what a usage type means, how to reduce usage, what changed over time, why they got a usage change alert, or whether a spike/drop alert was real or noisy. Also use before product-specific analytics skills when the user names a billable PostHog product metric such as events, recordings, feature flag requests, exceptions, survey responses, synced rows, logs, AI events, AI credits, or Inbox credits. Starts from Billing usage/spend tools, then routes to customer-visible product MCP surfaces for deeper investigation.
More in Research & Analysis
Microsoft Docs
microsoft
Looks up official Microsoft documentation to explain concepts, tutorials, configuration, limits and best practices.
Wiki Researcher
microsoft
Conducts multi-turn, evidence-grounded deep research on how a specific system or pattern works inside a codebase.
Wiki Qa
microsoft
Answers questions about a code repository using source-file evidence and inline citations.
Notion Research Documentation
openai
Researches Notion pages and synthesizes findings into cited briefs, comparisons, or reports published back to Notion.
Notion Meeting Intelligence
openai
Prepares meeting agendas and pre-reads using Notion context and research, tailored to attendees and meeting type.
Research Ops
affaan-m
Routes research requests to the right evidence-gathering workflow and reports findings with labeled evidence types.