DEDUPED Hot AI repos, turned into use cases Get 5 a day

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

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

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.

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

The problemCopying data by hand from a logged-in web page into a spreadsheet is slow and error-prone.

The outcomeAn editable sheet artifact kept in the session, built from the data you selected on the page.

What you need first

  • Chrome 135 or newer
  • An OpenAI-compatible API key to paste into the side panel (BYOK)
  • Developer mode enabled on chrome://extensions
  • A clone of the repo or a Release zip download

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 for your agent

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.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page