
browser-test
UI test recipe -- composes browser-record (capture) + browser-replay (verify) so every test produces a replayable RVF artifact, not an ephemeral run
- Installs
- 755
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/ruvnet/ruflo --skill browser-test- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads browser-test automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
- Record the test run by composing
browser-record:- Allocates an RVF container with
--kind browser-session. - Begins a ruvector trajectory.
- Allocates an RVF container with
- Drive interactions —
browser_open,browser_click,browser_fill,browser_type,browser_select. Each action emits atrajectory-step. - Wait for elements / network idle via
browser_waitbefore assertions. - Validate with
browser_get-text/browser_get-value/browser_get-title/browser_get-url. Validation outcomes go intofindings.mdinside the RVF container. - Screenshot before / after key interactions for visual regression. Filenames follow
<step-id>.png. - Snapshot the accessibility tree at navigation boundaries.
- End the session:
trajectory-end --verdict pass|fail,rvf compact, AgentDB index inbrowser-sessions. - (Optional) Diff against
--against <prior-session-id>: invokebrowser-screenshot-diffto compare the new run with a baseline.
Navigation
browser_back/browser_forwardfor history navigationbrowser_reloadto refresh the pagebrowser_scrollto scroll to elements or coordinates
What changed from v0.1.0
- The skill no longer ends with
browser_closealone — it ends with the session-end protocol. - Selectors discovered during the test land in
browser-selectors(host:intent), so the next test can find them by embedding similarity. - Validation outputs pass
aidefence_is_safebefore any LLM-facing summary; injection-flagged content is quarantined tofindings.md. - The same skill, used in CI, now produces an artifact that
/ruflo-browser replaycan re-drive.
Tips
- Use
browser_waitbefore assertions to handle async rendering. - For visual regression, save the parent session id and pass
--against <id>on the next run. - Use
browser_evalfor custom JavaScript assertions — but redact any returned strings via theaidefence_is_safegate before logging.
FAQ
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 browser-test?
Run npx skills add https://github.com/ruvnet/ruflo --skill browser-test in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/browser-test/ (personal) or .claude/skills/browser-test/ (project).
Which AI agents can use browser-test?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is browser-test safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains browser-test?
It is published by ruvnet in ruvnet/ruflo. It has 755 recorded installs.
More from ruvnet/ruflo
swarm-orchestration
ruvnet/ruflo
Multi-agent swarm coordination for complex tasks. Uses hierarchical topology with specialized agents to break down and execute complex work across multiple files and modules. Use when: 3+ files need changes, new feature implementation, cross-module refactoring, API changes with tests, security-related changes, performance optimization across codebase, database schema changes. Skip when: single file edits, simple bug fixes (1-2 lines), documentation updates, configuration changes, quick exploration.
agent-arch-system-design
ruvnet/ruflo
Agent skill for arch-system-design - invoke with $agent-arch-system-design
agent-workflow
ruvnet/ruflo
Agent skill for workflow - invoke with $agent-workflow
security-audit
ruvnet/ruflo
Comprehensive security scanning and vulnerability detection. Includes input validation, path traversal prevention, CVE detection, and secure coding pattern enforcement. Use when: authentication implementation, authorization logic, payment processing, user data handling, API endpoint creation, file upload handling, database queries, external API integration. Skip when: read-only operations on public data, internal development tooling, static documentation, styling changes.
github-project-management
ruvnet/ruflo
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Popular testing & qa skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
grilling
mattpocock/skills
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
migrate-to-shoehorn
mattpocock/skills
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
run-train
lllllllama/rigorpilot-skills
Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized trainoutputs/. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.
test-driven-development
obra/superpowers
Use when implementing any feature or bugfix, before writing implementation code
finishing-a-development-branch
obra/superpowers
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work