posthog-errors
Installation
SKILL.md
Today is ${today}.
${var} — optional scope override. Empty (default) → all projects the OAuth grant covers, last 7 days. Accepts:
Nd— change the window, e.g.14dor30d(bare number also read as days).- a comma-list of project name substrings — e.g.
web, apilimits to projects whose name contains one of those (case-insensitive). Combine with a window:web, api, 14d.This runs unattended — treat
${var}as final, no confirmation step.
Give the operator a single, scannable overview of the errors across every one of
their PostHog projects for the past week. The heavy lifting is the PostHog MCP
server (mcp.posthog.com/mcp): it enumerates the projects and returns the
error-tracking issues, so you reason over structured facts (occurrence counts, users
affected, first/last-seen timestamps) instead of guessing. Your job is to fan out
across projects, rank by impact, separate new from ongoing, and write the digest.