Agent skill · Testing & QA

browser-test

UI test recipe -- composes browser-record (capture) + browser-replay (verify) so every test produces a replayable RVF artifact, not an ephemeral run

rUv71,307★ · +1,002/wk · 3 repos on radarProfile →
claude-codecodexread-onlyMIT
Install
npx skills add ruvnet/ruflo --skill browser-test --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Allowed tools: mcp__plugin_ruflo-core_ruflo__browser_openmcp__plugin_ruflo-core_ruflo__browser_clickmcp__plugin_ruflo-core_ruflo__browser_fillmcp__plugin_ruflo-core_ruflo__browser_typemcp__plugin_ruflo-core_ruflo__browser_pressmcp__plugin_ruflo-core_ruflo__browser_checkmcp__plugin_ruflo-core_ruflo__browser_uncheckmcp__plugin_ruflo-core_ruflo__browser_selectmcp__plugin_ruflo-core_ruflo__browser_hovermcp__plugin_ruflo-core_ruflo__browser_waitmcp__plugin_ruflo-core_ruflo__browser_screenshotmcp__plugin_ruflo-core_ruflo__browser_snapshot
Path: plugins/ruflo-browser/skills/browser-test/SKILL.md
Open the folder on GitHub →
Where it comes from
Source: ruvnet/ruflo
Stars: 67,015 · +629 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Browser Test Automated UI testing. **Now backed by a recorded RVF session container** instead of an ephemeral run, so every test produces a replayable artifact. ## When to use - Verifying UI functionality, user flows, or that frontend changes work in a real browser. - Producing a baseline session that future regressions can diff against. - Re-running a stored test session when CI fails (no need to re-author the test). ## Steps 1. **Record the test run** by composing `browser-record`: - Allocates an RVF container with `--kind browser-session`. - Begins a ruvector trajectory. 2. **Drive interactions** — `browser_open`, `browser_click`, `browser_fill`, `browser_type`, `browser_select`. Each action emits a `trajectory-step`. 3. **Wait** for elements / network idle via `browser_wait` before assertions. 4. **Validate** with `browser_get-text` / `browser_get-value` / `browser_get-title` / `browser_get-url`. Validation outcomes go into `findings.md` inside the RVF container. 5. **Screenshot** before / after key interactions for visual regression. Filenames follow `<step-id>.png`. 6. **Snapshot** the accessibility tree at navigation boundaries. 7. **End** the session: `trajectory-end --ve

What's inside
Steps it walks through
  1. When to use
  2. Steps
  3. Navigation
  4. What changed from v0.1.0
  5. Tips
More from ruflo
All skills →
About this skill
What does the browser-test skill do?

UI test recipe -- composes browser-record (capture) + browser-replay (verify) so every test produces a replayable RVF artifact, not an ephemeral run

How do I install it?

Run `npx skills add ruvnet/ruflo --skill browser-test --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From ruvnet/ruflo, a repository with 67,015 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going