ncklrs/claude-chrome-user-testing/session-recorder
Claude Code and agent skill by ncklrs/claude-chrome-user-testing
- community
Checking that the SKILL.md file is still in the repository.
Install
npx vskill@latest install ncklrs/claude-chrome-user-testing/session-recorderSKILL.md
Session Recorder Skill
Record user testing sessions as Playwright Traces for replay and analysis. Traces capture the full testing session including screenshots, DOM snapshots, network requests, and console logs.
When to Use
--recordflag is present in the command- User wants to replay or share a testing session
- Need to debug issues found during testing
- Creating documentation of UX issues
Trace File Format
Playwright Trace files (.zip) contain:
- Screenshots: Captured at each action
- DOM Snapshots: Full page state at each step
- Network Requests: All HTTP requests/responses
- Console Logs: JavaScript console output
- Action Timeline: Timestamped sequence of all interactions
Implementation
Starting a Recording
At the beginning of a test session when --record flag is present:
Stopping a Recording
At the end of a test session:
Trace Filename Convention
Format: {command}-{persona}-{YYYY-MM-DD-HHmmss}.zip
Examples:
user-test-genz-digital-native-2025-01-06-143022.zipstripe-test-impulse-buyer-2025-01-06-143156.zipuser-test-boomer-tech-averse-2025-01-06-150830.zip
Generating Filename
Recording Flow
1. Pre-Test Setup
When --record flag is detected:
2. During Test
- All browser interactions are automatically captured
- Screenshots taken at each action
- Network requests logged
- No additional steps needed
3. Post-Test Cleanup
Viewing Traces
Traces can be viewed at: https://trace.playwright.dev
Instructions for Users
- Open trace.playwright.dev in browser
- Drag and drop the
.ziptrace file - Explore the timeline:
- Click actions to see screenshots
- View network requests tab
- Check console output
- See DOM snapshots at each step
Trace Viewer Features
| Tab | Description | |
|---|---|---|
| Actions | Timeline of all interactions | |
| Network | HTTP requests and responses | |
| Console | JavaScript console output | |
| Source | (Optional) Source code context |
Integration with Test Modes
Standard Mode
Quiet Mode (--quiet --record)
Multi-Persona Mode (--personas --record)
Each persona test gets its own trace file:
Error Handling
Tracing Not Supported
If browser doesn't support tracing:
Directory Creation Failed
If recordings directory can't be created:
Trace Save Failed
If trace file can't be saved:
Best Practices
- Use with CI/CD: Combine
--recordwith--quietfor automated testing - Share Traces: Trace files are self-contained, easily shareable
- Storage: Traces can be large (10-50MB); manage storage accordingly
- Privacy: Traces may contain sensitive data; handle appropriately
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/session-recorder/SKILL.md
Popularity
- Repository stars
- 20
- Repository forks
- 2
- 7-day trend score
- 15
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/ncklrs/claude-chrome-user-testing/session-recorder)