Posthog Incident Runbook
jeremylongshore/tons-of-skills-marketplace
Triage a production PostHog integration incident while preserving application availability and evidence.
Triage PostHog error tracking issues during a daily or on-call review.
Install Triaging Error Issues
$ npx skills add PostHog/posthog --skill triaging-error-issues -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog triaging-error-issues --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/products/error_tracking/skills/triaging-error-issues .claude/skills/triaging-error-issues && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "triaging-error-issues" agent skill from https://github.com/PostHog/posthog/tree/master/products/error_tracking/skills/triaging-error-issues into .claude/skills/triaging-error-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triaging-error-issues", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/PostHog/posthog/tree/master/products/error_tracking/skills/triaging-error-issuesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add PostHog/posthog --skill triaging-error-issues -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog triaging-error-issues --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .agents/skills && cp -r skills-src/products/error_tracking/skills/triaging-error-issues .agents/skills/triaging-error-issues && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "triaging-error-issues" agent skill from https://github.com/PostHog/posthog/tree/master/products/error_tracking/skills/triaging-error-issues into .agents/skills/triaging-error-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triaging-error-issues", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PostHog/posthog --skill triaging-error-issues -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog triaging-error-issues --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/products/error_tracking/skills/triaging-error-issues .cursor/skills/triaging-error-issues && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "triaging-error-issues" agent skill from https://github.com/PostHog/posthog/tree/master/products/error_tracking/skills/triaging-error-issues into .cursor/skills/triaging-error-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triaging-error-issues", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/PostHog/posthog.git --path products/error_tracking/skills/triaging-error-issues--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add PostHog/posthog --skill triaging-error-issues -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog triaging-error-issues --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/products/error_tracking/skills/triaging-error-issues .gemini/skills/triaging-error-issues && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "triaging-error-issues" agent skill from https://github.com/PostHog/posthog/tree/master/products/error_tracking/skills/triaging-error-issues into .gemini/skills/triaging-error-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triaging-error-issues", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install PostHog/posthog triaging-error-issuesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add PostHog/posthog --skill triaging-error-issues -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .github/skills && cp -r skills-src/products/error_tracking/skills/triaging-error-issues .github/skills/triaging-error-issues && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "triaging-error-issues" agent skill from https://github.com/PostHog/posthog/tree/master/products/error_tracking/skills/triaging-error-issues into .github/skills/triaging-error-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triaging-error-issues", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PostHog/posthog --skill triaging-error-issues -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install PostHog/posthog triaging-error-issues --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/products/error_tracking/skills/triaging-error-issues .opencode/skills/triaging-error-issues && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "triaging-error-issues" agent skill from https://github.com/PostHog/posthog/tree/master/products/error_tracking/skills/triaging-error-issues into .opencode/skills/triaging-error-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triaging-error-issues", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
triaging-error-issues- GitHub stars
- 40k
- Token cost
- ~1.9k tokens
- SKILL.md length
- 812 words
- Files
- 1
- Skills in repo
- 252
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Triage PostHog error tracking issues during a daily or on-call review.
- Works in 5 steps: Pick a window and a signal → Pull the candidate list → Filter the noise → …
- The user asks whats broken?
- SKILL.md covers Available tools, Workflow, Tips and Related skills
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Triaging Error Issues is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Triage PostHog error tracking issues during a daily or on-call review. Use when the user asks "what's broken?", "what new errors do we have?", "show me top errors today", "what should I look at this morning", or wants a prioritized list of active issues to work on. Surfaces new and high-impact issues, ranks by users affected and recency, points at linked replays, and proposes next actions (investigate, assign, suppress, merge).
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Incident response. It works with PostHog. The repository describes itself as: :hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error…
When your agent uses it
- The user asks whats broken?
- What new errors do we have?
- Show me top errors today
- What should I look at this morning
Example prompts
- “s broken?”
- “what new errors do we have?”
- “show me top errors today”
- “/triaging-error-issues”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Pick a window and a signal
- Pull the candidate list
- Filter the noise
- Add context for the top items
- Present the triage list
What it can do on your machine
Read from SKILL.md and the folder at commit 812e5c6. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Triaging Error Issues loads about 1.9k tokens when it runs. Until then it costs about 113 tokens; SKILL.md has 812 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 812 words (~1,932 tokens).
“When a user asks "what's broken?" or wants a daily error review, the goal is a short prioritized list of issues worth a human's attention — not a dump of every active issue. Most projects have hundreds of active issues…”
- name
- triaging-error-issues
Files
Just SKILL.md in products/error_tracking/skills/triaging-error-issues of PostHog/posthog.
Open the folder on GitHubat commit 812e5c6
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in PostHog/posthog, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Triaging Error Issues next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Triaging Error Issues this skillPostHog/posthog | 40k | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Posthog Incident Runbookjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Kubernetes Network Root Cause Analysiskubeshark/kubeshark | 12k | — | ~5.3k | Automated safety check: Pass | Apache-2.0 | |
| UModel Root Cause Analysisalibaba/UnifiedModel | 415 | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Telemetry AnalyticsOpenHands/OpenHands | 90k | — | ~305 | Automated safety check: Pass | MIT | |
| Learningskortix-ai/suna | 20k | — | ~1.1k | Automated safety check: Pass | Custom licence |
Similar skills
Kubernetes Network Root Cause Analysis
kubeshark/kubeshark
Investigates past Kubernetes incidents from Kubeshark traffic snapshots: takes captures, dissects API calls, extracts PCAPs and compares traffic over time.
UModel Root Cause Analysis
alibaba/UnifiedModel
Investigates a service incident to its root cause by querying a UModel object graph alongside metrics, logs, topology and recent deployments.
Telemetry Analytics
OpenHands/OpenHands
This skill should be used when the user asks to "add tracking", "add a PostHog event", "change telemetry consent", "instrument onboarding", "debug analytics", or changes telemetry.ts…
Learnings
kortix-ai/suna
The project's episodic memory: a timestamped ledger of rules paid for with real outages and near-misses, one entry per incident.
Oncall
pigweed-project/pigweed
Pigweed oncall rotation runbooks and maintenance workflows (such as rolling CIPD client tools for b/315378787).
More from PostHog/posthog
All 252 skills in this repo- Official
Authoring Log Alerts
PostHog/posthog
Author useful, low-noise log alerts on services in a PostHog project.
- Official
Autoresolving PR Conflicts
PostHog/posthog
Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…
- Official
Diagnosing Stacktrace Symbolication
PostHog/posthog
Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM).
- Official
Exploring Apm Traces
PostHog/posthog
Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.
- Official
Exploring LLM Traces
PostHog/posthog
Debug and inspect LLM/AI agent traces using PostHog's MCP tools.
- Official
Investigate Metric
PostHog/posthog
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
Related
Works with
Categories
Questions about Triaging Error Issues
What does Triaging Error Issues do?
Triage PostHog error tracking issues during a daily or on-call review. Triaging Error Issues is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Triage PostHog error tracking issues during a daily or on-call review.
When should I use Triaging Error Issues?
Triaging Error Issues fits situations like: the user asks whats broken?; what new errors do we have?; show me top errors today; what should I look at this morning.
How do I install Triaging Error Issues in Claude Code?
Run `npx skills add PostHog/posthog --skill triaging-error-issues -a claude-code`. Or copy the skill folder (products/error_tracking/skills/triaging-error-issues in PostHog/posthog) into .claude/skills/triaging-error-issues in your project. Claude Code loads it when a task matches its description.
How do I install Triaging Error Issues in Codex?
Run `npx skills add PostHog/posthog --skill triaging-error-issues -a codex`. Or copy the skill folder (products/error_tracking/skills/triaging-error-issues in PostHog/posthog) into .agents/skills/triaging-error-issues in your project. Codex loads it when a task matches its description.
Can I use Triaging Error Issues in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PostHog/posthog --skill triaging-error-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/triaging-error-issues, .gemini/skills/triaging-error-issues, .github/skills/triaging-error-issues and .opencode/skills/triaging-error-issues in your project.
What does Triaging Error Issues need to run?
SKILL.md names no scripts, command-line tools or credentials: Triaging Error Issues is instructions for the agent only.
Does Triaging Error Issues access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Triaging Error Issues safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Triaging Error Issues use?
Triaging Error Issues has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Triaging Error Issues use?
About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Triaging Error Issues?
Skills that share tags, products or a category with Triaging Error Issues: Posthog Incident Runbook (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Kubernetes Network Root Cause Analysis (kubeshark/kubeshark, 12k stars), UModel Root Cause Analysis (alibaba/UnifiedModel, 415 stars) and Telemetry Analytics (OpenHands/OpenHands, 90k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Triaging Error Issues?
PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,200 GitHub stars. The repository holds 252 skills in this directory. The repository was last updated on October 9, 2026.
Source: PostHog/posthog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.