Integration Expo
adrianhajdin/react-native-recurrly
PostHog integration for Expo applications. An agent skill from adrianhajdin/react-native-recurrly.
Guides a user from "I want to watch recordings but don't know which ones" to a short, high-signal list of sessions worth watching.
Install Finding Sessions To Watch
$ npx skills add PostHog/posthog --skill finding-sessions-to-watch -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog finding-sessions-to-watch --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-sessions-to-watch .claude/skills/finding-sessions-to-watch && 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-sessions-to-watch" agent skill from https://github.com/PostHog/posthog/tree/master/products/replay/skills/finding-sessions-to-watch into .claude/skills/finding-sessions-to-watch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finding-sessions-to-watch", 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-sessions-to-watchType 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-sessions-to-watch -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog finding-sessions-to-watch --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-sessions-to-watch .agents/skills/finding-sessions-to-watch && 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-sessions-to-watch" agent skill from https://github.com/PostHog/posthog/tree/master/products/replay/skills/finding-sessions-to-watch into .agents/skills/finding-sessions-to-watch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finding-sessions-to-watch", 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-sessions-to-watch -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog finding-sessions-to-watch --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-sessions-to-watch .cursor/skills/finding-sessions-to-watch && 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-sessions-to-watch" agent skill from https://github.com/PostHog/posthog/tree/master/products/replay/skills/finding-sessions-to-watch into .cursor/skills/finding-sessions-to-watch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finding-sessions-to-watch", 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-sessions-to-watch--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-sessions-to-watch -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog finding-sessions-to-watch --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-sessions-to-watch .gemini/skills/finding-sessions-to-watch && 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-sessions-to-watch" agent skill from https://github.com/PostHog/posthog/tree/master/products/replay/skills/finding-sessions-to-watch into .gemini/skills/finding-sessions-to-watch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finding-sessions-to-watch", 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-sessions-to-watchInstalls 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-sessions-to-watch -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-sessions-to-watch .github/skills/finding-sessions-to-watch && 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-sessions-to-watch" agent skill from https://github.com/PostHog/posthog/tree/master/products/replay/skills/finding-sessions-to-watch into .github/skills/finding-sessions-to-watch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finding-sessions-to-watch", 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-sessions-to-watch -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-sessions-to-watch --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-sessions-to-watch .opencode/skills/finding-sessions-to-watch && 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-sessions-to-watch" agent skill from https://github.com/PostHog/posthog/tree/master/products/replay/skills/finding-sessions-to-watch into .opencode/skills/finding-sessions-to-watch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finding-sessions-to-watch", 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-sessions-to-watch- GitHub stars
- 40k
- Token cost
- ~2.6k tokens
- SKILL.md length
- 975 words
- Files
- 1
- Skills in repo
- 252
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Guides a user from "I want to watch recordings but don't know which ones" to a short, high-signal list of sessions worth watching.
- Works in 5 steps: Pin down the goal → Discover before you filter → Run a minimal query → …
- The user asks which sessions
- SKILL.md covers The one rule, Available tools, Workflow and Starting points → filters, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Finding Sessions To Watch is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Guides a user from "I want to watch recordings but don't know which ones" to a short, high-signal list of sessions worth watching. Use when the user asks which sessions or replays to watch, wants help finding interesting / useful recordings, says they don't know where to start in session replay, or wants to watch sessions about a goal (signup, pricing, onboarding, checkout, a feature, rageclicks, errors, mobile, a specific person) without naming exact filters. Turns a vague intent into a focused RecordingsQuery…
Its SKILL.md is about 2.6k 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 Mobile. 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
- The user asks which sessions
- Replays to watch
- Wants help finding interesting / useful recordings
- Says they dont know where to start in session replay
Example prompts
- “I want to watch recordings but don”
- “Use the finding-sessions-to-watch skill to guide a user from "I want to watch recordings but don't know which ones" to a short, high-signal list of…”
- “/finding-sessions-to-watch”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Pin down the goal
- Discover before you filter
- Run a minimal query
- Triage and present
- Offer the next step
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 Sessions To Watch loads about 2.6k tokens when it runs. Until then it costs about 203 tokens; SKILL.md has 975 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 975 words (~2,573 tokens).
“Most people open session replay with a goal ("why are signups dropping?") but no idea which of thousands of recordings to watch. A raw, unfiltered list is the worst possible answer — it buries the useful sessions in noise. Your…”
- name
- finding-sessions-to-watch
Files
Just SKILL.md in products/replay/skills/finding-sessions-to-watch 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 Sessions To Watch 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 Sessions To Watch this skillPostHog/posthog | 40k | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Integration Expoadrianhajdin/react-native-recurrly | 102 | — | ~664 | Automated safety check: Pass | None | |
| Zafer Skillszaferayan/skills | 113 | — | ~8.5k | Automated safety check: Notes | None | |
| Define Feature Flagmacro-inc/macro | 4.6k | — | ~780 | Automated safety check: Pass | AGPL-3.0 | |
| Compare Array Bundle SizePostHog/posthog-js | 628 | — | ~599 | Automated safety check: Pass | Custom licence | |
| Integration Astro Staticwill-be-done/will-be-done | 152 | — | ~636 | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Zafer Skills
zaferayan/skills
Expo React Native mobile app development with StoreKit 2 subscriptions (expo-iap) plus RevenueCat observer mode, AdMob ads with UMP/ATT consent, PostHog analytics, i18n with RTL, onboarding flow…
Define Feature Flag
macro-inc/macro
Define a frontend feature flag with defineFlag and wire its readers.
- 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.
Integration Astro Static
will-be-done/will-be-done
PostHog integration for static Astro sites using SSG. An agent skill from will-be-done/will-be-done.
Posthog Instrumentation
trycompai/crm
Automatically add PostHog analytics instrumentation to code.
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
Categories
Questions about Finding Sessions To Watch
What does Finding Sessions To Watch do?
Guides a user from "I want to watch recordings but don't know which ones" to a short, high-signal list of sessions worth watching. Finding Sessions To Watch is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Guides a user from "I want to watch recordings but don't know which ones" to a short, high-signal list of sessions worth watching.
When should I use Finding Sessions To Watch?
Finding Sessions To Watch fits situations like: the user asks which sessions; replays to watch; wants help finding interesting / useful recordings; says they dont know where to start in session replay.
How do I install Finding Sessions To Watch in Claude Code?
Run `npx skills add PostHog/posthog --skill finding-sessions-to-watch -a claude-code`. Or copy the skill folder (products/replay/skills/finding-sessions-to-watch in PostHog/posthog) into .claude/skills/finding-sessions-to-watch in your project. Claude Code loads it when a task matches its description.
How do I install Finding Sessions To Watch in Codex?
Run `npx skills add PostHog/posthog --skill finding-sessions-to-watch -a codex`. Or copy the skill folder (products/replay/skills/finding-sessions-to-watch in PostHog/posthog) into .agents/skills/finding-sessions-to-watch in your project. Codex loads it when a task matches its description.
Can I use Finding Sessions To Watch 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-sessions-to-watch -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-sessions-to-watch, .gemini/skills/finding-sessions-to-watch, .github/skills/finding-sessions-to-watch and .opencode/skills/finding-sessions-to-watch in your project.
What does Finding Sessions To Watch need to run?
SKILL.md names no scripts, command-line tools or credentials: Finding Sessions To Watch is instructions for the agent only.
Does Finding Sessions To Watch 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 Sessions To Watch 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 Sessions To Watch use?
Finding Sessions To Watch 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 Sessions To Watch use?
About 2.6k tokens (SKILL.md is roughly 10k 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 Sessions To Watch?
Skills that share tags, products or a category with Finding Sessions To Watch: Integration Expo (adrianhajdin/react-native-recurrly, 102 stars), Zafer Skills (zaferayan/skills, 113 stars), Define Feature Flag (macro-inc/macro, 4.6k stars) and Compare Array Bundle Size (PostHog/posthog-js, 628 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Finding Sessions To Watch?
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.