session-replay
Skill116 starsChanged 11 months agoMITView on GitHub
Set up session replay for visual debugging. Use when implementing screen recording, replay features, or visual debugging tools.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- guangda88/LingClaudetheir own version, first seen Nov 1, 2026
- issue-orchestrator/issue-orchestratortheir own version, first seen Sep 6, 2026
- JDerekLomas/claude-code-skillstheir own version, first seen Jan 14, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- issue-orchestrator/issue-orchestrator★ 10same name
- guangda88/LingClaude★ 1same name
- JDerekLomas/claude-code-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- crash-instrumentationSkill
- instrumentation-planningSkill
- interaction-latencySkill
- navigation-latencySkill
- network-tracingSkill
- symbolication-setupSkill
- user-journey-trackingSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
All text input fields
- Distinctive: line 52
Don't record everything. Target:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Session Replay
Capture visual recordings of user sessions for debugging.
When to Use
- Reproducing hard-to-debug issues
- Understanding user confusion
- QA and support investigations
Privacy Requirements (Must Do)
Mask by default:
- All text input fields
- Passwords and sensitive data
- User-generated content
- Financial information
- User photos/documents
Performance Budget
| Resource | Limit |
| CPU | <5% additional |
| Memory | <20MB additional |
| Network | Batch on WiFi |
| Battery | Pause when low |
Capture Strategies
| Strategy | Fidelity | Overhead |
| Screenshots (1-2 fps) | Lower | Lower |
| View hierarchy recording | Higher | Moderate |
| Hybrid (screenshots + events) | Best | Moderate |
Best Practice
Don't record everything. Target:
- Error sessions only (rolling buffer)
- Key user journeys
- 1-10% sampling for general insights
Implementation
See references/session-replay.md for:
- Platform-specific setup
- Privacy masking patterns
- Vendor configurations (Sentry, Datadog, New Relic)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.