# OpenClaw Browser Prompts

URL: https://stevekinney.com/courses/openclaw/openclaw-browser-prompts
Canonical: https://stevekinney.com/courses/openclaw/openclaw-browser-prompts
Author: Steve Kinney
Language: en-US
Modified: 2026-10-08T12:11:12.000Z
Description: Two example prompts that put OpenClaw's browser to work: researching GitHub Trending and running an exploratory QA pass on a web app.
Course: OpenClaw
Course URL: https://stevekinney.com/courses/openclaw

---

These prompts assume the browser is already set up. If you haven't turned it on yet, start with [Setting Up and Using the Browser](browser-setup-and-use.md).

Here is an example prompt that you might consider:

```md
Open GitHub Trending at https://github.com/trending.

Find the 10 most interesting repositories related to AI agents, developer tooling, or automation.

For each repository:

- Open its repository page.
- Read its README.
- Check its recent activity and open issues.
- Determine what makes it interesting or technically distinctive.
- Identify potential shortcomings or limitations.

Rank the repositories by how useful they might be for someone building sophisticated AI agent workflows.

Produce a report containing a comparison table, links, and your top three recommendations.

Use the browser to navigate the actual GitHub interface. Don't substitute web search. Explain what you're doing as you navigate, and take screenshots of three interesting discoveries.
```

Or, here is an even more fun one:

```md
You are a senior QA engineer evaluating a web application.

Open https://todomvc.com/examples/react/dist/.

Your task is to explore the application and discover its functionality without being given a test plan.

First, inspect the interface and identify the available features.

Then design and execute a comprehensive exploratory test plan using the browser.

Test:

- Creating tasks
- Editing existing tasks
- Completing and reopening tasks
- Filtering active and completed tasks
- Deleting tasks
- Clearing completed tasks
- Persistence across page reloads
- Keyboard interactions
- Edge cases involving empty input and unusual characters

For each test, record the expected behavior, observed behavior, and pass/fail result.
Capture screenshots of any unexpected behavior.

Finish with a QA report containing:

- Features discovered
- Tests executed
- Bugs or inconsistencies identified
- Reproduction steps for each issue
- Recommendations for improving the application

**Important**: Actually interact with the application using browser tools. Do not infer behavior from the source code or documentation. Never report a test as passing unless you executed it.
```