Agent skill · microsoft
validate-ui-scenario
Use when reproducing a UI bug or verifying a fix by driving a real VS Code window end to end and capturing evidence. Writes a scenario file, runs it against a dev build or installed Insiders, and produces a captioned video, per-step screenshots, a Playwright trace, and an HTML report to attach to an issue or pull request.
What it needs
About 7k tokens when loaded.
What this skill does
Validate UI Scenario Drives a real VS Code instance through a scenario and records reproducible evidence. Use this to reproduce a reported bug, to show that a fix works, or to attach a recording to a test-plan item. For deterministic regression coverage that runs on every build, write a smoke test instead (see the smoke-tests skill) — this skill is for one-off, issue-derived validation. A scenario is a small JavaScript file run by test/scenario/out/runScenario.js. Nothing else has to be configured: the runner launches VS Code, records video and a trace, captures a screenshot at every step boundary, writes the report, and captions the recording with each step and its result. Prepare Check ffmpeg and ffprobe are available before running. The runner looks on PATH and in the usual install locations, so an ffmpeg installed after the editor started is still found. Without them the scenario still runs and keeps the raw recording, but the video is not captioned with step titles. The runner warns at startup; if they are missing, tell the user how to install them rather than silently returning an unannotated video: Platform Install ---------- --------- Windows winget install Gyan.FFmpeg macOS brew install ffmpeg Linux sudo apt install ffmpeg A new terminal may be needed for PATH to pick them up, or set FFMPEGPATH and FFPROBEPATH. An existing run can be annotated afterwards with node test/scenario/out/renderEvidenceChapters.js <run-dir>. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills microsoft/validate-ui-scenario