agentleFS
Sign inStart free
Kripu77Kripu77/software-factory/skills/browser-use/SKILL.md

browser-use

Skill7 starsChanged 3 months agoMITView on GitHub

Drive a real browser to QA a running app. Screenshots, clicks, forms, evidence. Use when there is no Playwright suite, or when a human flow must be walked.

  • Reads credentials

54 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use context7-efficient, configuring-dapr-pubsub and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • hfzarslanSkill

    context7-efficient

    Token-efficient library documentation fetcher using Context7 MCP with 86.8% token savings through intelligent shell pipeline filtering. Fetches code examples, API references, and best practices for JavaScript, Python, Go, Rust, and other libraries. Use when users ask about library documentation, need code examples, want API usage patterns, are learning a new framework, need syntax reference, or troubleshooting with library-specific information. Triggers include questions like "Show me React hooks", "How do I use Prisma", "What's the Next.js routing syntax", or any request for library/framework documentation.

    Also in 5 projects that use this

  • AbdullahMalik17Skill

    configuring-dapr-pubsub

    Configures Dapr pub/sub components for event-driven microservices with Kafka or Redis. Use when wiring agent-to-agent communication, setting up event subscriptions, or integrating Dapr sidecars. Covers component configuration, subscription patterns, publishing events, and Kubernetes deployment. NOT when using direct Kafka clients or non-Dapr messaging patterns.

    Also in 3 projects that use this

  • AbdullahMalik17Skill

    deploying-cloud-k8s

    Deploys applications to cloud Kubernetes (AKS/GKE/DOKS) with CI/CD pipelines. Use when deploying to production, setting up GitHub Actions, troubleshooting deployments. Covers build-time vs runtime vars, architecture matching, and battle-tested debugging.

    Also in 3 projects that use this

  • dycnnnbSkill

    remote-browser

    Controls a cloud browser from a sandboxed remote machine. Use when the agent is running in a sandbox (no GUI) and needs to navigate websites, interact with web pages, fill forms, take screenshots, or expose local dev servers via tunnels.

    Also in 3 projects that use this

  • mjunaidcaSkill

    building-chatgpt-apps

    Guides creation of ChatGPT Apps with interactive widgets using OpenAI Apps SDK and MCP servers. Use when building ChatGPT custom apps with visual UI components, embedded widgets, or rich interactive experiences. Covers widget architecture, MCP server setup with FastMCP, response metadata, and Developer Mode configuration. NOT when building standard MCP servers without widgets (use building-mcp-servers skill instead).

    Also in 3 projects that use this

  • mjunaidcaSkill

    building-chat-interfaces

    Build AI chat interfaces with custom backends, authentication, and context injection. Use when integrating chat UI with AI agents, adding auth to chat, injecting user/page context, or implementing httpOnly cookie proxies. Covers ChatKitServer, useChatKit, and MCP auth patterns. NOT when building simple chatbots without persistence or custom agent integration.

    Also in 3 projects that use this

  • +6 more from AbdullahMalik17

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 53 edited versions we read keep these.

  • 3

    Distinctive

    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:

    Stop and say the harness has no browser.

    line 20
  2. Distinctive:

    Do not invent a headless stack.

    line 22
  3. Very specific:

    If login or 2FA is required, stop and hand that step to a human.

    line 29
  4. Distinctive:

    Prefer a real click over injecting JS.

    line 35

“Common” is measured: kept by at least 6 in 10 of the 53 edited versions of this file we could read. “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 use

Trigger

Need to test a running web app by actually using it. No smoke suite, or the suite does not cover this flow.

Navigate, click, fill, screenshot, assert. Use the harness browser.

How to drive the browser

Pick the door the runner actually has, in this order:

  1. A first-party browser tool on this harness (Grok Bot browserUse, Grok Build browser, Claude computer use).
  2. Headed Playwright against the given URL, if Playwright is already in the checkout.
  3. Stop and say the harness has no browser.

Do not invent a headless stack. Do not scrape cookies out of a profile to skip login.

Workflow

  1. Resolve the target URL (dispatched, or local app for the repo). Confirm it is up before clicking.
  2. Walk the flow as a user. One path. Screenshot each meaningful step.
  3. Assert what the user would see: copy, state, error, navigation.
  4. If login or 2FA is required, stop and hand that step to a human. Never ask for a password in chat. Never read .env.
  5. Report. Repro, screenshots, what broke, what was fine.

Guardrails

  • Report only. Do not patch product code.
  • Prefer a real click over injecting JS.
  • Deterministic waits for visible state, not sleep.
  • Stay on the dispatched flow. Do not wander the whole site.
  • Never merge.

Output

  • Flow walked
  • Screenshots of evidence
  • Failures with repro steps
  • Anything that could not be tested (auth wall, downed app)

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