Skip to main content
skill CX Codex

investigating-logs — Claude Code skill for log analysis

The investigating-logs Claude Code skill investigates logs in a PostHog project, checks service health and traces error spikes. It runs for deploy checks, incident triage, change analysis, or a search around one trace or run.

no license 188 installs ★ 101 updated 2026-11-16

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add PostHog/ai-plugin --skill investigating-logs -a claude-code
Open on GitHub

What investigating-logs does

The skill examines PostHog project logs to help identify service health, changes in message patterns, and reasons for error spikes. It starts with summaries and comparisons across time windows; raw log rows come later. Summaries first.

PostHog tools group entries by service, severity, and pattern, track counts over time, and retrieve context around a log line, trace, or run. A post-change check compares windows on either side of the change; it needs a time boundary to make that comparison meaningful. The skill can also locate logs tied to an alert or user complaint.

What it helps with

  • check whether a service still emits logs after a deployment
  • find new error patterns after a configuration change
  • break an error spike down by time window
  • inspect log context around a trace or run
  • identify which service is involved in an incident

Example prompts for the agent

  • Check the PostHog project logs after the latest deployment and compare them with the earlier period.
  • Why did the error count rise? Investigate the spike in the logs.
  • Find the logs around this trace and explain what happened.

How to install investigating-logs

1Skills CLI (Vercel)

npx skills add PostHog/ai-plugin --skill investigating-logs -a claude-code

2Manually: put the files in place

~/.claude/skills/investigating-logs/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/investigating-logs/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about investigating-logs

How do I install investigating-logs in Claude Code?

Run npx skills add PostHog/ai-plugin --skill investigating-logs -a claude-code. The skill file is placed at ~/.claude/skills/investigating-logs/SKILL.md.

What does investigating-logs do?

It investigates logs in a PostHog project, checking service health, comparing message patterns across time windows, and retrieving context around a trace or run. Raw rows are used for deeper investigation.

How does investigating-logs check whether a deploy caused problems?

It compares error patterns and log volume from before and after the change, then drills into suspicious rows. The comparison needs the change time as a boundary.

Similar skills

All skills for DevOps and infrastructure →

From the same set82

The whole set →
signals-scout-web-vitals signals-scout-web-vitals tracks page p75 LCP, INP, CLS, and FCP from PostHog events, spots performance degradation against Google thresholds, and links regressions to deploys. CX Codex +1 194installs signals-scout-skills-store signals-scout-skills-store audits shared PostHog agent skills for vague descriptions, oversized bodies, broken links, and leaked secrets. Produces reports with copy-ready fixes. CX Codex +1 193installs analyzing-expensive-users analyzing-expensive-users — a skill for Claude Code, Codex, Cursor and other agents that finds the top spenders in PostHog AI observability and explains what drives their costs. CX Codex +1 192installs turning-engineering-analytics-into-insights turning-engineering-analytics-into-insights — a skill for Claude Code and Codex: converts PR and CI metrics into saved PostHog insights, dashboards, and automated subscriptions. Triggers when visualizing engineering team performance. CX Codex +1 189installs investigating-ci-failures The investigating-ci-failures Claude Code skill traces an individual CI failure to its likely cause. It separates PR-specific problems from default-branch breaks and flaky tests. CX Codex +1 188installs review-hog-validation-criteria review-hog-validation-criteria serves as a final PR review gate, filtering candidate findings to keep real defects while discarding speculative noise. CX Codex +1 187installs review-hog-blind-spots-general The review-hog-blind-spots-general skill looks for concrete problems that earlier reviewers missed in a PR chunk. Use it as a final pass after other review perspectives have reported their findings. CX Codex +1 187installs review-hog-authoring review-hog-authoring — a guide skill for writing custom PostHog Review pieces: extra PR perspectives, your own blind-spot sweep, and the bars that decide what gets published or fixed. CX Codex +1 187installs

Project sponsors

Companies that keep this analytics open