recording-e2e

Automate end-to-end validation of display recording and replay pipelines.

2|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/lovon-spec/intendant --skill recording-e2e
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recording-e2e
Source: https://github.com/lovon-spec/intendant/tree/main/tests/skills/recording-e2e
Command: npx skills add https://github.com/lovon-spec/intendant --skill recording-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end validation of the display recording and replay pipeline in the Intendant environment, reducing manual QA effort and ensuring the flow from display capture to web UI playback works reliably.

Core Features & Use Cases

  • End-to-end test orchestrations for display recording, Xvfb lifecycle, and ffmpeg-based segment generation.
  • Verifies HTTP endpoints (/recordings, /debug) and browser-based replay UI for accurate playback.
  • Provides guidance for setup, prerequisites, and troubleshooting to reproduce recording scenarios consistently.

Quick Start

Configure a temporary intendant.toml with recording enabled, start Xvfb and x11vnc, then launch intendant with --web and verify the /recordings API and replay UI.

Frequently Asked Questions about recording-e2e

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate an Xvfb and ffmpeg display recording pipeline end-to-end?

You validate an Xvfb and ffmpeg display recording pipeline by automating the capture workflow, serving segments via HTTP endpoints, and verifying browser UI replay. This orchestrates the entire flow to reduce manual QA effort and ensure reliable playback.

What prerequisites do I need to automate display recording tests with ffmpeg?

To automate display recording tests, you need Xvfb, Firefox, x11vnc, ffmpeg, curl, and xdotool installed. You also need a configured intendant.toml file and a web interface to exercise the recording flow.

How does browser-based replay UI validation work for ffmpeg screen captures?

Browser-based replay UI validation works by launching Xvfb, capturing display output with ffmpeg, serving segments through /recordings and /debug HTTP endpoints, and verifying accurate playback within a browser UI like Firefox.

Can I verify the /recordings and /debug HTTP endpoints using curl during display capture?

Yes, you can verify the /recordings and /debug HTTP endpoints using curl. The pipeline expects these endpoints to serve generated ffmpeg segments, allowing you to confirm the recording flow works correctly before browser replay.