Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →remotion-dev/react-scan
Capture and analyze Remotion Studio React render profiles with the internal React Scan Lite collector.
Passed 13 of 20 test cases with the skill, and 8 of 20 without it.
and 7 more in the full report
6 fixed9 passed either way8 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
When performing an interaction profile session in Studio using browser automation, what function call sequence initiates and ends the recording, and how many times should the user action be repeated?
| Checked | Without skill | With skill |
|---|---|---|
| Calls `start_react_scan_recording` before the interaction and `stop_react_scan_recording` immediately after. | Missed | Passed |
| Executes the named interaction exactly three times during the recording period. | Missed | Passed |
The instructions your model reads when the skill loads.
Use targeted captures to optimize measured Studio interactions. Do not infer a performance problem from source alone when the workflow can be reproduced.
Start from the repository root:
bun run react-scan:capture
For the Brand Studio, run:
bun run react-scan:capture:brand
Wait for Studio to finish building, open the printed Studio URL with the browser, and let the page settle. The React Scan WebMCP tools are only registered in this development capture mode.
Call start_react_scan_recording, then use browser-use to perform one named
interaction three times. Call stop_react_scan_recording immediately
afterwards. Keep the recording short so startup, HMR, and unrelated interactions
do not dominate the data. Call get_react_scan_recording to return the raw
events and an agent-oriented summary.
After retrieving the recording, stop Studio with Ctrl+C. Recordings only live in the WebMCP result; React Scan does not send them to a separate HTTP collector.
React Scan replaces the React DevTools profiling-hook channel while active. Do not record with the React DevTools Timeline Profiler at the same time.
Read the summary returned by get_react_scan_recording first. Confirm the
capture contains commit events and inspect profilingHooksStatuses; do not
interpret a missing profiling channel as an idle application.
test cases passed, vs 8 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.