# AI use cases for Browser Kitten (Player-YN/BrowserKitten)

Repo: [Player-YN/BrowserKitten](https://github.com/Player-YN/BrowserKitten) | Use cases: 3 | Page: https://dedupedai.com/use-cases/player-yn-browserkitten/

Paw Work is an unpacked Chrome extension that runs an AI agent in a side panel to act on your live, logged-in browser tab and produce sheet, document, or site HTML files.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Turn data on a logged-in page into an editable sheet: https://dedupedai.com/use-cases/player-yn-browserkitten/turn-page-data-into-editable-sheet/
- Draft a site HTML artifact from a live browser session: https://dedupedai.com/use-cases/player-yn-browserkitten/draft-site-html-from-browser-session/
- Run regression tests before changing the extension: https://dedupedai.com/use-cases/player-yn-browserkitten/run-regression-tests-before-extension-change/

## How to turn data on a logged-in page into an editable sheet with Browser Kitten

Repo: [Player-YN/BrowserKitten](https://github.com/Player-YN/BrowserKitten) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Select the data on a live page, describe the result, and get a sheet artifact you can edit.

**Who it is for:** An analyst or operations person who needs a table from a web app they are already signed into and has no export button for.

**The problem:** Copying data by hand from a logged-in web page into a spreadsheet is slow and error-prone.

**The outcome:** An editable sheet artifact kept in the session, built from the data you selected on the page.

### Steps

1. Clone the repo or download a Release zip and unzip it.
2. In Chrome, open chrome://extensions, turn on Developer mode, click Load unpacked, and select the folder that contains manifest.json.
3. Open the side panel, paste your OpenAI-compatible API key, and open a normal http(s) page with the data.
4. Select the table or fields on the page, describe the sheet you want, and send the task.
5. Check the sheet artifact against the page before you use it.

### Prompt to paste into your agent

```text
Using the Paw Work extension in the PawWork repo, load the unpacked extension, select the data on <target page URL> in the side panel, and ask for an editable sheet artifact with the selected fields. Verify that the row count in the sheet matches the rows visible on the page.
```

### Caveat

The README links Release downloads to Player-YN/PawWork_ZhuaZhua while this repo is listed as Browser Kitten, so confirm you are loading the intended build.

Risk, credentials: The agent works inside a Chrome profile where you are already logged in, and your API key is stored in chrome.storage.local, so use a key with limited scope.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/player-yn-browserkitten/turn-page-data-into-editable-sheet/

## How to draft a site HTML artifact from a live browser session with Browser Kitten

Repo: [Player-YN/BrowserKitten](https://github.com/Player-YN/BrowserKitten) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Ask the side-panel agent to build a site HTML artifact based on what is open in your tab.

**Who it is for:** A small team member or solo builder who wants a quick HTML page based on content they are viewing in Chrome.

**The problem:** Rebuilding a page layout from content already open in the browser takes time when you have to switch between tools.

**The outcome:** A site HTML artifact kept in the session that you can review and reuse.

### Steps

1. Load the unpacked extension as described in the Load it section of the README.
2. Paste your OpenAI-compatible API key into the side panel.
3. Open the source page on a normal http(s) site and select the content you want.
4. Describe the HTML page you want and send the task.
5. Open the site HTML artifact and review its markup before reuse.

### Prompt to paste into your agent

```text
Using the PawWork extension, select the content on <source page URL> in the side panel and request a site HTML artifact with a simple layout for that content. Verify that the artifact includes every heading and paragraph you selected.
```

### Caveat

The README does not describe how site HTML artifacts are published or hosted, so treat the output as a local file in the session.

Risk, remote script: The agent can run guest JavaScript against the browser through sys.eval, so review what it runs before you enable Allow User Scripts.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/player-yn-browserkitten/draft-site-html-from-browser-session/

## How to run regression tests before changing the extension with Browser Kitten

Repo: [Player-YN/BrowserKitten](https://github.com/Player-YN/BrowserKitten) | Difficulty: Advanced | Time: 30 minutes | Basis: From the README

Run the Node and browser smoke tests to confirm a baseline before editing Paw Work.

**Who it is for:** A developer who wants to modify the extension and needs a known-good baseline first.

**The problem:** Edits to an agent extension can break runtime behavior that is hard to spot by reading code.

**The outcome:** A pass or fail result for the pure Node regression suite and the browser smoke test on the unmodified code.

### Steps

1. Clone the repo and open a terminal in its root folder.
2. Run `node --test tests/runtime-regression.test.mjs` to execute the pure Node regression tests.
3. Run `node tests/browser-smoke.cjs` to load the real extension and run the smoke test.
4. If the browser smoke test fails with CDP_BUSY, close DevTools on the target tab and run it again.
5. Record the results before you make your change.

### Prompt to paste into your agent

```text
In the PawWork repo at <repo path>, run `node --test tests/runtime-regression.test.mjs` and then `node tests/browser-smoke.cjs`. Report the pass or fail count for each and list any failing test name. Verify that the Node suite runs without a browser.
```

### Caveat

The browser smoke test loads the real extension, so it needs Chrome installed and a clean target tab, and the README gives no further setup detail.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/player-yn-browserkitten/run-regression-tests-before-extension-change/