Opik Analytics Instrumentation
comet-ml/opik
Shows how to add product analytics events to Opik's frontend, Java backend and Python SDK, all reporting through Segment to PostHog with an opik_ name prefix.
Finds the most informative session recording linked to an error tracking issue.
OfficialCustom licenceAuto-check passed
Install Finding Replay For Issue
$ npx skills add PostHog/posthog --skill finding-replay-for-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog finding-replay-for-issue --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/replay/skills/finding-replay-for-issue .claude/skills/finding-replay-for-issue && 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 "finding-replay-for-issue" agent skill from https://github.com/PostHog/posthog/tree/master/products/replay/skills/finding-replay-for-issue into .claude/skills/finding-replay-for-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finding-replay-for-issue", 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/replay/skills/finding-replay-for-issueType 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 finding-replay-for-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog finding-replay-for-issue --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/replay/skills/finding-replay-for-issue .agents/skills/finding-replay-for-issue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "finding-replay-for-issue" agent skill from https://github.com/PostHog/posthog/tree/master/products/replay/skills/finding-replay-for-issue into .agents/skills/finding-replay-for-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finding-replay-for-issue", 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 finding-replay-for-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog finding-replay-for-issue --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/replay/skills/finding-replay-for-issue .cursor/skills/finding-replay-for-issue && 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 "finding-replay-for-issue" agent skill from https://github.com/PostHog/posthog/tree/master/products/replay/skills/finding-replay-for-issue into .cursor/skills/finding-replay-for-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finding-replay-for-issue", 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/replay/skills/finding-replay-for-issue--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 finding-replay-for-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog finding-replay-for-issue --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/replay/skills/finding-replay-for-issue .gemini/skills/finding-replay-for-issue && 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 "finding-replay-for-issue" agent skill from https://github.com/PostHog/posthog/tree/master/products/replay/skills/finding-replay-for-issue into .gemini/skills/finding-replay-for-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finding-replay-for-issue", 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 finding-replay-for-issueInstalls 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 finding-replay-for-issue -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/replay/skills/finding-replay-for-issue .github/skills/finding-replay-for-issue && 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 "finding-replay-for-issue" agent skill from https://github.com/PostHog/posthog/tree/master/products/replay/skills/finding-replay-for-issue into .github/skills/finding-replay-for-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finding-replay-for-issue", 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 finding-replay-for-issue -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 finding-replay-for-issue --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/replay/skills/finding-replay-for-issue .opencode/skills/finding-replay-for-issue && 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 "finding-replay-for-issue" agent skill from https://github.com/PostHog/posthog/tree/master/products/replay/skills/finding-replay-for-issue into .opencode/skills/finding-replay-for-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finding-replay-for-issue", 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
finding-replay-for-issue- GitHub stars
- 40k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 670 words
- Files
- 1
- Skills in repo
- 252
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Finds the most informative session recording linked to an error tracking issue.
- Works in 4 steps: Get the issue details → Find sessions with this error → Rank the candidates → …
- A user has an error tracking issue ID and wants to watch a replay showing what the user was doing when the error occurred
- 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
Finding Replay For Issue is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Finds the most informative session recording linked to an error tracking issue. Use when a user has an error tracking issue ID and wants to watch a replay showing what the user was doing when the error occurred. Ranks linked sessions by recency, activity score, and journey completeness, then summarizes the pre-error context. Replaces blind session picking from potentially hundreds of linked recordings.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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
- A user has an error tracking issue ID and wants to watch a replay showing what the user was doing when the error occurred
Example prompts
- “Use the finding-replay-for-issue skill to find the most informative session recording linked to an error tracking issue”
- “/finding-replay-for-issue”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Get the issue details
- Find sessions with this error
- Rank the candidates
- Present the finding
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 and sql).
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
Finding Replay For Issue loads about 1.7k tokens when it runs. Until then it costs about 108 tokens; SKILL.md has 670 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 670 words (~1,686 tokens).
“When a user says "show me a replay for this error" or "find a recording for issue X", the goal isn't just any linked session — it's the one that best shows what led to the error. Popular issues can…”
- name
- finding-replay-for-issue
Files
Just SKILL.md in products/replay/skills/finding-replay-for-issue 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
Finding Replay For Issue 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 |
|---|---|---|---|---|---|---|
| Finding Replay For Issue this skillPostHog/posthog | 40k | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| Opik Analytics Instrumentationcomet-ml/opik | 22k | — | ~4.4k | Automated safety check: Pass | Apache-2.0 | |
| C15tc15t/c15t | 1.9k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Define Feature Flagmacro-inc/macro | 4.6k | — | ~780 | Automated safety check: Pass | AGPL-3.0 | |
| Soku CLIAbout-Intelligence/soku-cli | 305 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Compare Array Bundle SizePostHog/posthog-js | 628 | — | ~599 | Automated safety check: Pass | Custom licence |
Similar skills
C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Define Feature Flag
macro-inc/macro
Define a frontend feature flag with defineFlag and wire its readers.
Soku CLI
About-Intelligence/soku-cli
Guides an agent through the soku command line tool for ads, GA4 and PostHog data reads, ads writes, SEO hosting, automations, files and skill management.
- Official
Compare Array Bundle Size
PostHog/posthog-js
Quickly compare the posthog-js array.js bundle size in the current working tree against a git baseline using the repository's esbuild proxy.
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…
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
Questions about Finding Replay For Issue
What does Finding Replay For Issue do?
Finds the most informative session recording linked to an error tracking issue. Finding Replay For Issue is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Finds the most informative session recording linked to an error tracking issue.
When should I use Finding Replay For Issue?
Finding Replay For Issue fits situations like: A user has an error tracking issue ID and wants to watch a replay showing what the user was doing when the error occurred.
How do I install Finding Replay For Issue in Claude Code?
Run `npx skills add PostHog/posthog --skill finding-replay-for-issue -a claude-code`. Or copy the skill folder (products/replay/skills/finding-replay-for-issue in PostHog/posthog) into .claude/skills/finding-replay-for-issue in your project. Claude Code loads it when a task matches its description.
How do I install Finding Replay For Issue in Codex?
Run `npx skills add PostHog/posthog --skill finding-replay-for-issue -a codex`. Or copy the skill folder (products/replay/skills/finding-replay-for-issue in PostHog/posthog) into .agents/skills/finding-replay-for-issue in your project. Codex loads it when a task matches its description.
Can I use Finding Replay For Issue 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 finding-replay-for-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/finding-replay-for-issue, .gemini/skills/finding-replay-for-issue, .github/skills/finding-replay-for-issue and .opencode/skills/finding-replay-for-issue in your project.
What does Finding Replay For Issue need to run?
SKILL.md names no scripts, command-line tools or credentials: Finding Replay For Issue is instructions for the agent only.
Does Finding Replay For Issue 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 Finding Replay For Issue 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 Finding Replay For Issue use?
Finding Replay For Issue 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 Finding Replay For Issue use?
About 1.7k tokens (SKILL.md is roughly 6.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 Finding Replay For Issue?
Skills that share tags, products or a category with Finding Replay For Issue: Opik Analytics Instrumentation (comet-ml/opik, 22k stars), C15t (c15t/c15t, 1.9k stars), Define Feature Flag (macro-inc/macro, 4.6k stars) and Soku CLI (About-Intelligence/soku-cli, 305 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Finding Replay For Issue?
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.