by Player-YN
Paw Work - selection-first web agent for Chrome: select on the live page, describe the outcome, take away an editable office file. BYOK, sandboxed, no server.
# Add to your Claude Code skills
git clone https://github.com/Player-YN/PawWork_ZhuaZhuaGuides for using ai agents skills like PawWork_ZhuaZhua.
PawWork_ZhuaZhua is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by Player-YN. Paw Work - selection-first web agent for Chrome: select on the live page, describe the outcome, take away an editable office file. BYOK, sandboxed, no server. It has 80 GitHub stars.
PawWork_ZhuaZhua's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/Player-YN/PawWork_ZhuaZhua" and add it to your Claude Code skills directory (see the Installation section above).
PawWork_ZhuaZhua is primarily written in JavaScript. It is open-source under Player-YN on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh PawWork_ZhuaZhua against similar tools.
No comments yet. Be the first to share your thoughts!
Unlocks once the catalog security scan passes (runs nightly).
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
Select on the live page. Describe the outcome. Take away a real file.
English · 中文
[!IMPORTANT] Just want to use Paw Work? Do not clone this whole repository. You do not need the developer files. Clone only branch
unpacked(~44 MB). That folder is the Chrome extension (manifest.jsonat the root).Clone creates
paw-workunder the directory where you run the command, not a fixed Desktop path. If you run it from your user home, that isC:\Users\yyy\paw-work. Git cannot print the path by itself — the last line of the block below does. In Chrome, Load unpacked that printed folder.Windows (PowerShell) — paste this whole block:
git clone --depth 1 --single-branch --branch unpacked https://github.com/Player-YN/PawWork_ZhuaZhua.git paw-work (Get-Item .\paw-work).FullNamemacOS / Linux:
git clone --depth 1 --single-branch --branch unpacked https://github.com/Player-YN/PawWork_ZhuaZhua.git paw-work realpath paw-workThen: Chrome →
chrome://extensions→ Developer mode → Load unpacked → select the folder whose path was just printed.No git? On this GitHub page: Code → switch the branch to
unpacked→ Download ZIP. Unzip, then Load unpacked the folder that containsmanifest.json.Optional, same bytes: the Release zip (
paw-work-unpacked.zip). Unzip and Load unpacked the innerpaw-workfolder.
SELECT + DESCRIBE OUTCOME → DELIVER
What you can do · See it · How it works · Install · Trust · Limitations
Paw Work is a Chrome MV3 extension. Turn Paw Mode on, point at images, tables, text, blocks, or links on the page you already have open, then say what you want in the sidepanel. It returns editable office files on live canvases — not a chat essay about the page.
It is not an unattended Operator that roams the web for you, and not a terminal coding agent. It sits beside the browser world you are already logged into: you set the scope, it returns something you can check.
| For | Not a first choice for |
|---|---|
| People who already work in the browser — compare, extract, export, turn a page into a sheet, deck, poster, site, or long doc | Unattended RPA (cross-site checkout, submit, pay) |
| Work that starts on a page you are already looking at (shop, SaaS, docs, article) | A coding-agent home: Docker, local shell, million-file repos |
No account. No server. You bring your own model keys.
| On the page | You ask for | You take away |
|---|---|---|
| Product photos, tables, copy, blocks, links | “Make a comparison sheet” | A live spreadsheet (Univer) you can keep editing |
| The same selection, or a blank workspace | “Make an 8-page deck / one poster” | Design/Slides on a tldraw canvas; decks export to PPTX |
| The current page | “Make an editable site, with entrance motion” | Real HTML. Tweaks stay on that file. Site QA gates quality |
| Long notes or a transcript | “Turn this into a document” | A document canvas |
| Need a picture or a lookup | “Generate in this style / search, then put it in the sheet” | Images in the workspace; search uses your web-acquire key |
You can run more than one task in the same session. @ mentions a capture. Empty templates for sheet / slides / docs / site sit at the foot of the workspace rail.
Try asking:
Complex work can yield a plan card before it writes: Approve, Decline, or Required to change (you leave notes; it revises the plan; the old card stays). It does not silently expand outside what you selected.
Selecting product photos on a live Apple page. The sidepanel holds the capture; the next line is the outcome.

A live spreadsheet beside the sidepanel. The agent is splitting a SKU column on the open workbook — not dropping a second file into chat.

Live page (Paw on) → select → sidepanel → live canvas / file
Not listed on the Chrome Web Store yet. Passersby: clone only branch unpacked (see the box at the top) — do not clone this source tree. Then: Paw on → paste a model key → select something → say one sentence.
chrome.*, the live page DOM, or another session’s files. No executable code is loaded from a CDN.If you just want to use it — do not clone this whole repository. Clone only branch unpacked.
paw-work.chrome://extensionsmanifest.json is at that root)No git? Code → branch unpacked → Download ZIP, unzip, then steps 2–4. Same pack is also on the Release page as paw-work-unpacked.zip.
No Node, no npm install. Do not load the source-repo root.
Prerequisites: Node.js 20+, npm, Chrome 120+.
git clone https://github.com/Player-YN/PawWork_ZhuaZhua.git
cd PawWork_ZhuaZhua
npm install
npm run build:agent
npm run pack:extension
Then Load unpacked → artifacts/unpacked/. After npm install the folder is hundreds of megabytes (node_modules). Do not load the repository root. Rebuild (npm run build:agent) and reload after pulling.
How to build and test: CONTRIBUTING.md.
Nothing runs without them. Configure in the sidepanel settings.
Chrome MV3 extension. Sidepanel talks to an in-extension workspace (no Paw Work cloud). Spreadsheets and documents: Univer. Posters and slides: tldraw. Sites: real HTML. Generated JS runs in a local WASM sandbox. Files persist in the browser (IndexedDB + OPFS). MIT code in this repo; third-party engines in THIRD_PARTY_NOTICES.md.
Runtime contracts (isolation, writes, tools) live in docs/SESSION_WORKSPACE_RUNTIME.md and docs/PROMPT_RUNTIME.md. Host path: constitution § Host path.
unpacked (or the same-bytes Release zip). GitHub sideload is a stopgap; CWS is the later front door.MIT for the code in this repository — LICENSE. The source tree does not ship Univer/tldraw runtime bundles (you build those locally). The unpacked branch and the Release zip include those builds, plus a verbatim tldraw license.