agentleFS
Sign inStart free
salmandevsalmandev/everything-gemini/skills/browser-qa-tester/SKILL.md

browser-qa-tester

Skill2 starsChanged 28 days agoApache-2.0View on GitHub

Orchestrates automated UI, frontend, and end-to-end testing using Antigravity's native browser subagent with automatic WebP recording. Use when verifying web applications, visual bugs, or UI flows.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before launching the browser subagent, ensure the web app is running locally:

    line 19
  2. Very specific:

    If not running, launch with run_command and IsDaemon: true:

    line 24
  3. Distinctive:

    After the subagent finishes:

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Browser QA Tester

This skill automates visual testing and end-to-end verification of web applications using Antigravity's native browser_subagent.

Why Browser Subagent?

  • Autonomous Interaction: Navigates, clicks, fills inputs, and scrolls.
  • Automatic Recording: Automatically captures WebP video recordings saved directly into the conversation artifacts directory.
  • Console & Network Inspection: Intercepts unhandled errors, failed network requests, and visual layout glitches.

Verification Procedure

1. Ensure Local Server is Running

Before launching the browser subagent, ensure the web app is running locally:

# Check if port is open
lsof -i :3000 || lsof -i :5173

If not running, launch with run_command and IsDaemon: true:

npm run dev

2. Invoke browser_subagent

Formulate a precise task description with explicit stop conditions:

  • Specify target URL (e.g., http://localhost:3000).
  • Specify unique element IDs or text labels to click/type.
  • Define what constitutes success (e.g., "Verify dashboard renders after login").

3. Review Recording Artifacts

After the subagent finishes:

  • Embed the generated WebP recording into your summary artifact:
    ![Browser Test Recording](file:///absolute/path/to/artifacts/browser_test_demo.webp)
  • Summarize any console warnings or errors detected during the test.

For specialized testing recipes (Responsive testing, Form verification), see references/browser-recipes.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free