Logfire Query
pydantic/skills
Query and analyze Logfire telemetry data — traces, logs, spans, metrics, summaries, and SQL results.
Investigate logs in a PostHog project: verify a service or deployment is healthy, explain an error spike, triage an incident, or understand what a log stream is saying.
Install Investigating Logs
$ npx skills add PostHog/posthog --skill investigating-logs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog investigating-logs --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/logs/skills/investigating-logs .claude/skills/investigating-logs && 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 "investigating-logs" agent skill from https://github.com/PostHog/posthog/tree/master/products/logs/skills/investigating-logs into .claude/skills/investigating-logs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-logs", 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/logs/skills/investigating-logsType 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 investigating-logs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog investigating-logs --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/logs/skills/investigating-logs .agents/skills/investigating-logs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "investigating-logs" agent skill from https://github.com/PostHog/posthog/tree/master/products/logs/skills/investigating-logs into .agents/skills/investigating-logs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-logs", 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 investigating-logs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog investigating-logs --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/logs/skills/investigating-logs .cursor/skills/investigating-logs && 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 "investigating-logs" agent skill from https://github.com/PostHog/posthog/tree/master/products/logs/skills/investigating-logs into .cursor/skills/investigating-logs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-logs", 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/logs/skills/investigating-logs--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 investigating-logs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog investigating-logs --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/logs/skills/investigating-logs .gemini/skills/investigating-logs && 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 "investigating-logs" agent skill from https://github.com/PostHog/posthog/tree/master/products/logs/skills/investigating-logs into .gemini/skills/investigating-logs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-logs", 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 investigating-logsInstalls 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 investigating-logs -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/logs/skills/investigating-logs .github/skills/investigating-logs && 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 "investigating-logs" agent skill from https://github.com/PostHog/posthog/tree/master/products/logs/skills/investigating-logs into .github/skills/investigating-logs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-logs", 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 investigating-logs -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 investigating-logs --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/logs/skills/investigating-logs .opencode/skills/investigating-logs && 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 "investigating-logs" agent skill from https://github.com/PostHog/posthog/tree/master/products/logs/skills/investigating-logs into .opencode/skills/investigating-logs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-logs", 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
investigating-logs- GitHub stars
- 40k
- Token cost
- ~2.1k tokens
- SKILL.md length
- 942 words
- Files
- 1
- Skills in repo
- 252
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Investigate logs in a PostHog project: verify a service or deployment is healthy, explain an error spike, triage an incident, or understand what a log stream is saying.
- Works in 5 steps: Pin down the change time and the… → Orient with… → posthog:logs-patterns-diff with… → …
- The user asks to check the logs
- SKILL.md covers When to use this skill, When not to use this skill, Tools and Pick the workflow by question…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Investigating Logs is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Investigate logs in a PostHog project: verify a service or deployment is healthy, explain an error spike, triage an incident, or understand what a log stream is saying. Use when the user asks to "check the logs", asks whether a service, deploy, release, or change is working or broke anything, asks why errors are up or what changed, or wants the root cause of failures visible in logs. Routes the logs MCP tools (services overview, pattern mining, before/after pattern diffing, bucketed counts, facets, raw rows) so…
Its SKILL.md is about 2.1k 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 Databases, covering SQL, Root cause analysis and Deployment. It works with PostHog and SQL. 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 to check the logs
- Asks whether a service
- Change is working
- Asks why errors are up
Example prompts
- “check the logs”
- “/investigating-logs”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Pin down the change time and the affected service(s). Ask if the user hasn't said; the diff is meaningless without a boundary.
- Orient with posthog:logs-services-create: is the service still logging at all, and what is its error_rate now?
- posthog:logs-patterns-diff with query.dateRange from the change time to now and baselineDateRange
- Check volume continuity with posthog:logs-count-ranges spanning before and after the boundary
- Drill only the suspects: pivot each suspicious pattern to raw lines via its match_regex with posthog:query-logs.
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.
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
Investigating Logs loads about 2.1k tokens when it runs. Until then it costs about 158 tokens; SKILL.md has 942 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 942 words (~2,131 tokens).
“Investigation is a narrowing problem: summarize before you read. One posthog:logs-patterns call compresses millions of lines into at most 200 templates, and one posthog:logs-patterns-diff call answers "what is different about now vs. before" directly. Raw rows (posthog:query-logs) are the last…”
- name
- investigating-logs
Files
Just SKILL.md in products/logs/skills/investigating-logs 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
Investigating Logs 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 |
|---|---|---|---|---|---|---|
| Investigating Logs this skillPostHog/posthog | 40k | — | ~2.1k | Automated safety check: Pass | Custom licence | |
| Logfire Querypydantic/skills | 140 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Flux Migratejeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.9k | Automated safety check: Notes | MIT | |
| Cloudflare 3sundial-org/awesome-openclaw-skills | 663 | — | ~1.5k | Automated safety check: Pass | None | |
| Test The Docssupabase/supabase | 111k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| GCP Cloud SQLsickn33/agentic-awesome-skills | 47k | 2 repos | ~2.4k | Automated safety check: Pass | MIT |
Similar skills
- Official
Flux Migrate
jeremylongshore/tons-of-skills-marketplace
Build zero-downtime database migrations — forward SQL, rollback SQL, deployment sequence.
Cloudflare 3
sundial-org/awesome-openclaw-skills
Manage Cloudflare Workers, KV, D1, R2, and secrets using the Wrangler CLI.
- Official
Test The Docs
supabase/supabase
Execute runnable docs snippets and examples inside a disposable Docker Compose sandbox (runner container + local Supabase stack via supabase start).
GCP Cloud SQL
sickn33/agentic-awesome-skills
Provision Cloud SQL and Spanner databases. An agent skill from sickn33/agentic-awesome-skills.
Ops Telemetry Query
boundless-xyz/boundless
Internal — for Boundless team members only. An agent skill from boundless-xyz/boundless.
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
Categories
Questions about Investigating Logs
What does Investigating Logs do?
Investigate logs in a PostHog project: verify a service or deployment is healthy, explain an error spike, triage an incident, or understand what a log stream is saying. Investigating Logs is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Investigate logs in a PostHog project: verify a service or deployment is healthy, explain an error spike, triage an incident, or understand what a log stream is saying.
When should I use Investigating Logs?
Investigating Logs fits situations like: the user asks to check the logs; asks whether a service; change is working; asks why errors are up.
How do I install Investigating Logs in Claude Code?
Run `npx skills add PostHog/posthog --skill investigating-logs -a claude-code`. Or copy the skill folder (products/logs/skills/investigating-logs in PostHog/posthog) into .claude/skills/investigating-logs in your project. Claude Code loads it when a task matches its description.
How do I install Investigating Logs in Codex?
Run `npx skills add PostHog/posthog --skill investigating-logs -a codex`. Or copy the skill folder (products/logs/skills/investigating-logs in PostHog/posthog) into .agents/skills/investigating-logs in your project. Codex loads it when a task matches its description.
Can I use Investigating Logs 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 investigating-logs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/investigating-logs, .gemini/skills/investigating-logs, .github/skills/investigating-logs and .opencode/skills/investigating-logs in your project.
What does Investigating Logs need to run?
SKILL.md names no scripts, command-line tools or credentials: Investigating Logs is instructions for the agent only.
Does Investigating Logs 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 Investigating Logs 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 Investigating Logs use?
Investigating Logs 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 Investigating Logs use?
About 2.1k tokens (SKILL.md is roughly 8.5k 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 Investigating Logs?
Skills that share tags, products or a category with Investigating Logs: Logfire Query (pydantic/skills, 140 stars), Flux Migrate (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Cloudflare 3 (sundial-org/awesome-openclaw-skills, 663 stars) and Test The Docs (supabase/supabase, 111k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Investigating Logs?
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.