PostHogProduct analytics platform, 40k+ GitHub stars312 installs on skills.shFinding Replay for Issue
Finds the most informative session recording linked to an error tracking issue.
3 static scans, 0 counted findings.
Edge checks it again each time your agent loads it.
From the posthog public repository. Edge did not write or edit this skill.
What it does
- 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.
Why PostHog
Open-source product analytics company. Each fact links its public source.
- Main repo
The posthog repo has 40k+ GitHub stars.
GitHub repo - Docs site repo
The posthog.com repo has 1.1k+ GitHub stars.
GitHub repo
Public sources, checked Oct 26, 2026.
How it works
- 1Copy
Try for free gives you one prompt.
- 2Paste
Paste it into Claude Code, Codex or Cursor.
- 3Ask
Ask for the outcome. Your agent loads Finding Replay for Issue.
3 static scans, 0 counted findings.
Security state at 2026-09-30: reviewed. Static scans check the code, not how well the skill works.
State definitionsSkill details
Security scansReviewed
3 static scans, 0 counted findings. Security state at 2026-09-30: reviewed. Edge checks it again each time your agent loads it.
Edge static checks (Edge-run): edge-static/1.0.1. Scope: Static patterns for remote execution, credentials with network sends, obfuscation, prompt overrides, hidden Unicode, binaries and persistence. Raw findings: .
Cisco skill-scanner (Edge-run): cisco-skill-scanner/2.1.0. Scope: Local static, YARA, pipeline and behavioral analyzers; no LLM or AI Defense analysis. Raw findings: 1.
Semgrep Edge rules (Edge-run): semgrep/1.178.0+edge-rules.c15016a36fd3+offline-v1. Scope: Six Edge-authored static rules with Semgrep CE; offline execution and metrics disabled. Semgrep-maintained rules excluded. Raw findings: .
- Edge static checks
- Pass · 0 counted findings · 2026-09-27
- Cisco skill-scanner
- Pass · 0 counted findings · 2026-09-27
- Semgrep Edge rules
- Pass · 0 counted findings · 2026-09-27
Creator, source & licenceposthog
From the posthog public repository. Edge did not write or edit this skill.
- Repository
- posthog/skills
- Skill file
- View source at revision
- Revision
- 835ceac8ec56af5ca9af647c815abc2fa6f9b330
- Package hash
- sha256:0c18ac5f14b7a9a34fabb9fe5ad8f6dc5c25a3adb28a96ba9e58800342323edf
- Licence
- MIT
- Description
- 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.
Quoted from the skill’s own description
Read skill files1 file
1 file, 6.6 KB at revision 835ceac8ec56.
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. Published by PostHog (posthog/skills).
Is Finding Replay for Issue safe to use?
Edge security state: Reviewed (3 Edge-run static scans, scanned Sep 30, 2026). The Evidence tab shows the scan.
How do I use Finding Replay for Issue in Claude Code, Codex or Cursor?
Click Try for free, pick your agent and follow its one step. Edge is free, with no Edge account.