Greptimedb Perses Dashboard
GreptimeTeam/dashboard
Generate Perses dashboards or single panels for GreptimeDB. An agent skill from GreptimeTeam/dashboard.
Debug and inspect LLM/AI agent traces using PostHog's MCP tools.
Install Exploring LLM Traces
$ npx skills add PostHog/posthog --skill exploring-llm-traces -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog exploring-llm-traces --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/ai_observability/skills/exploring-llm-traces .claude/skills/exploring-llm-traces && 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 "exploring-llm-traces" agent skill from https://github.com/PostHog/posthog/tree/master/products/ai_observability/skills/exploring-llm-traces into .claude/skills/exploring-llm-traces/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploring-llm-traces", 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/ai_observability/skills/exploring-llm-tracesType 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 exploring-llm-traces -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog exploring-llm-traces --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/ai_observability/skills/exploring-llm-traces .agents/skills/exploring-llm-traces && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "exploring-llm-traces" agent skill from https://github.com/PostHog/posthog/tree/master/products/ai_observability/skills/exploring-llm-traces into .agents/skills/exploring-llm-traces/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploring-llm-traces", 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 exploring-llm-traces -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog exploring-llm-traces --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/ai_observability/skills/exploring-llm-traces .cursor/skills/exploring-llm-traces && 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 "exploring-llm-traces" agent skill from https://github.com/PostHog/posthog/tree/master/products/ai_observability/skills/exploring-llm-traces into .cursor/skills/exploring-llm-traces/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploring-llm-traces", 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/ai_observability/skills/exploring-llm-traces--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 exploring-llm-traces -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog exploring-llm-traces --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/ai_observability/skills/exploring-llm-traces .gemini/skills/exploring-llm-traces && 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 "exploring-llm-traces" agent skill from https://github.com/PostHog/posthog/tree/master/products/ai_observability/skills/exploring-llm-traces into .gemini/skills/exploring-llm-traces/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploring-llm-traces", 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 exploring-llm-tracesInstalls 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 exploring-llm-traces -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/ai_observability/skills/exploring-llm-traces .github/skills/exploring-llm-traces && 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 "exploring-llm-traces" agent skill from https://github.com/PostHog/posthog/tree/master/products/ai_observability/skills/exploring-llm-traces into .github/skills/exploring-llm-traces/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploring-llm-traces", 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 exploring-llm-traces -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 exploring-llm-traces --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/ai_observability/skills/exploring-llm-traces .opencode/skills/exploring-llm-traces && 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 "exploring-llm-traces" agent skill from https://github.com/PostHog/posthog/tree/master/products/ai_observability/skills/exploring-llm-traces into .opencode/skills/exploring-llm-traces/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exploring-llm-traces", 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
exploring-llm-traces- GitHub stars
- 40k
- Token cost
- ~4.4k tokens
- SKILL.md length
- 1,671 words
- Files
- 10 (incl. scripts, references)
- Skills in repo
- 252
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Debug and inspect LLM/AI agent traces using PostHog's MCP tools.
- Works in 4 steps: Classify the URL → Browse trace summaries → Read the content needed for the… → …
- The user pastes a trace
- SKILL.md covers Available tools, Event hierarchy, Workflow: debug a trace or… and Withheld properties, plus 5 more sections
- Runs Python scripts from its folder; calls python3
What it does
Exploring LLM Traces is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Debug and inspect LLM/AI agent traces using PostHog's MCP tools. Use when the user pastes a trace or session URL (e.g. /ai-observability/traces/<id or /ai-observability/sessions/<id), asks to debug a trace, figure out what went wrong, check if an agent used a tool correctly, verify context/files were surfaced, inspect subagent behavior, investigate LLM decisions, or analyze token usage and costs. Also use when raw SQL/HogQL against events.properties.$aiinput / $aioutputchoices returns empty — message content…
Its SKILL.md is about 4.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including scripts and reference files (for example `references/events-and-properties.md`, `references/example-llm-traces-list.md` and `scripts/extract_conversation.py`).
It sits in DevOps & Cloud, covering Observability, MCP servers and SQL. 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 pastes a trace
- Session URL (e.g
Example prompts
- “/exploring-llm-traces”
Requirements
- Python 3
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Classify the URL
- Browse trace summaries
- Read the content needed for the investigation
- Parse large full-detail results with scripts
What it can do on your machine
Read from SKILL.md and the folder at commit 10f9ad7. 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
Ships 6 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3
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
Exploring LLM Traces loads about 4.4k tokens when it runs, and up to ~7.9k if it reads all its reference files. Until then it costs about 150 tokens; SKILL.md has 1,671 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); the scripts in this folder 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 1,671 words (~4,416 tokens).
“PostHog captures LLM/AI agent activity as traces. Each trace is a tree of events representing a single AI interaction — from the top-level agent invocation down to individual LLM API calls.”
- name
- exploring-llm-traces
Files
SKILL.md and 9 other files (scripts, references) in products/ai_observability/skills/exploring-llm-traces of PostHog/posthog.
- SKILL.md
- references/events-and-properties.md
- references/example-llm-trace.md.j2
- references/example-llm-traces-list.md
- scripts/extract_conversation.py
- scripts/extract_span.py
- scripts/print_summary.py
- scripts/print_timeline.py
- scripts/search_traces.py
- scripts/show_structure.py
Open the folder on GitHubat commit 10f9ad7
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
Exploring LLM Traces 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 |
|---|---|---|---|---|---|---|
| Exploring LLM Traces this skillPostHog/posthog | 40k | — | ~4.4k | Automated safety check: Pass | Custom licence | |
| Greptimedb Perses DashboardGreptimeTeam/dashboard | 111 | — | ~3.9k | Automated safety check: Pass | Apache-2.0 | |
| Rift Backend EffectCompound-inc/rift | 124 | — | ~1.8k | Automated safety check: Pass | Custom licence | |
| Mz Query TracingMaterializeInc/materialize | 6.4k | — | ~1.8k | Automated safety check: Pass | Custom licence | |
| Sf Datacloud RetrieveJaganpro/sf-skills | 424 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Sf Datacloud SegmentJaganpro/sf-skills | 424 | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
Rift Backend Effect
Compound-inc/rift
A skill your agent uses when adding, reviewing, or refactoring backend code in Rift's TanStack Start app that should follow apps/start/BACKENDEFFECTPLAYBOOK.md.
Mz Query Tracing
MaterializeInc/materialize
Debug SQL execution time via distributed tracing (OpenTelemetry / Tempo).
Sf Datacloud Retrieve
Jaganpro/sf-skills
Salesforce Data Cloud Retrieve phase. An agent skill from Jaganpro/sf-skills.
Sf Datacloud Segment
Jaganpro/sf-skills
Salesforce Data Cloud Segment phase. An agent skill from Jaganpro/sf-skills.
TMA1 Observability Query
tma1-ai/tma1
Answers questions about agent spend, token use, traces, events, errors and tool usage by running read-only SQL against a local TMA1 observability store.
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
Investigate Metric
PostHog/posthog
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
- Official
QA Team
PostHog/posthog
Multi-agent QA review team for code changes. An agent skill from PostHog/posthog.
Related
Categories
Questions about Exploring LLM Traces
What does Exploring LLM Traces do?
Debug and inspect LLM/AI agent traces using PostHog's MCP tools. Exploring LLM Traces is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Debug and inspect LLM/AI agent traces using PostHog's MCP tools.
When should I use Exploring LLM Traces?
Exploring LLM Traces fits situations like: the user pastes a trace; session URL (e.g.
How do I install Exploring LLM Traces in Claude Code?
Run `npx skills add PostHog/posthog --skill exploring-llm-traces -a claude-code`. Or copy the skill folder (products/ai_observability/skills/exploring-llm-traces in PostHog/posthog) into .claude/skills/exploring-llm-traces in your project. Claude Code loads it when a task matches its description.
How do I install Exploring LLM Traces in Codex?
Run `npx skills add PostHog/posthog --skill exploring-llm-traces -a codex`. Or copy the skill folder (products/ai_observability/skills/exploring-llm-traces in PostHog/posthog) into .agents/skills/exploring-llm-traces in your project. Codex loads it when a task matches its description.
Can I use Exploring LLM Traces 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 exploring-llm-traces -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/exploring-llm-traces, .gemini/skills/exploring-llm-traces, .github/skills/exploring-llm-traces and .opencode/skills/exploring-llm-traces in your project.
What does Exploring LLM Traces need to run?
Going by SKILL.md and its folder, Exploring LLM Traces needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Exploring LLM Traces 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 Exploring LLM Traces 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Exploring LLM Traces use?
Exploring LLM Traces 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 Exploring LLM Traces use?
About 4.4k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.5k tokens, read only when the agent opens those files.
What are the alternatives to Exploring LLM Traces?
Skills that share tags, products or a category with Exploring LLM Traces: Greptimedb Perses Dashboard (GreptimeTeam/dashboard, 111 stars), Rift Backend Effect (Compound-inc/rift, 124 stars), Mz Query Tracing (MaterializeInc/materialize, 6.4k stars) and Sf Datacloud Retrieve (Jaganpro/sf-skills, 424 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Exploring LLM Traces?
PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,182 GitHub stars. The repository holds 252 skills in this directory. The repository was last updated on October 8, 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.