← Back to Skills Marketplace
weread_assitant
by
MingChaoXu
· GitHub ↗
· v1.0.1
· MIT-0
86
Downloads
0
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install weread-assitant
Description
Sync WeRead shelf state, reading progress, visible book content, and note-ready Markdown into a local workspace using the user's logged-in Chrome session. Us...
Usage Guidance
This skill appears to do what it claims, but review these points before installing:
- Understand local access: it drives your local Chrome (via a CDP proxy) and will load WeRead pages using your existing login — the browser will send your session cookies to WeRead even though the code does not read cookie/localStorage values itself. Only run it on machines you control.
- obsidian-cli trust: publishing is done by invoking obsidian-cli with the generated Markdown. Confirm obsidian-cli is the official tool you installed and that your vault configuration is correct.
- CDP proxy origin: the scripts call a local endpoint (http://localhost:3456). Ensure that proxy is indeed local and not forwarding requests to a remote host you don't control.
- Privacy hygiene: inspect output/ before sharing, avoid bulk exports unless you understand privacy/legal implications, and disable Chrome remote debugging when not in use.
If you need higher assurance, you can audit the small extraction functions (scripts/*) — they are readable and explicitly focus on visible DOM/text extraction — or run the scripts in a sandboxed account/vault first.
Capability Analysis
Type: OpenClaw Skill
Name: weread-assitant
Version: 1.0.1
The skill bundle facilitates syncing WeRead bookshelf data and book content into Obsidian notes. It employs high-risk capabilities, specifically browser automation via the Chrome DevTools Protocol (CDP) to interact with a user's logged-in session (found in scripts/cdp-client.mjs, scripts/fetch-book.mjs, and scripts/fetch-shelf.mjs) and local shell command execution using execFile to interface with the obsidian-cli (scripts/publish-obsidian.mjs). While these actions are consistent with the stated purpose and the project includes a detailed SECURITY.md acknowledging these risks, the combination of browser control and host-level command execution constitutes a significant attack surface that warrants a suspicious classification.
Capability Tags
Capability Assessment
Purpose & Capability
The skill claims to sync WeRead visible content into Obsidian and the code implements exactly that: it drives a local CDP proxy (http://localhost:3456), evaluates DOM extraction scripts, writes JSON/Markdown under output/, and calls obsidian-cli to publish notes. Required external pieces (Chrome logged-in session, Chrome remote debugging, and a local CDP proxy provided by a 'web-access' skill) are documented in SKILL.md. There are no unrelated credentials, third-party cloud APIs, or surprising binaries requested.
Instruction Scope
Runtime instructions and scripts consistently limit what is collected to visible DOM/text and metadata for a shelf or one book, and the SKILL.md + SECURITY.md explicitly state they do not read cookies or browser storage. The scripts execute page-level JS via CDP to extract text, then write local files and optionally call obsidian-cli. Note: because the skill loads pages in your already-logged-in Chrome session, the browser will send cookies to WeRead when loading pages (the code does not programmatically read cookie/localStorage values, but page loads will be authenticated by the browser). This is expected for the described use but is a privacy consideration.
Install Mechanism
There is no automated install script or external downloads; the repo is instruction-only and uses local node scripts. This minimizes installation risk — nothing is fetched from remote URLs or installed automatically by the skill itself.
Credentials
The skill requests no environment variables or secrets. It does require local capabilities: a running Chrome instance with remote debugging enabled and a local CDP proxy (http://localhost:3456), plus obsidian-cli if you want automated publishing. These requirements are proportionate to the purpose, but they do grant the skill the ability to read personal reading data from your logged-in browser and to modify an Obsidian vault via obsidian-cli; ensure you trust obsidian-cli and the local environment providing the CDP proxy.
Persistence & Privilege
The skill does not request 'always: true' or other elevated platform privileges. It writes files under its own output/ workspace and invokes obsidian-cli to publish notes; it does not modify other skills or system-wide agent config. Autonomous invocation is allowed (platform default) but not combined with unusual privileges.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install weread-assitant - After installation, invoke the skill by name or use
/weread-assitant - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
weread-assistant 1.0.1
- Added repository metadata and security files: .gitignore, LICENSE, and SECURITY.md.
- Updated documentation in SKILL.md to clarify least-privilege operation: only visible DOM is captured, no browser storage or cookies collected.
- Enhanced operating guidance to emphasize security boundaries and minimal data collection.
- Minor output clarification and additional privacy notes.
v1.0.0
这个skill可以让openclaw 和 微信读书联通,通过obsidian自动同步读书笔记
Metadata
Frequently Asked Questions
What is weread_assitant?
Sync WeRead shelf state, reading progress, visible book content, and note-ready Markdown into a local workspace using the user's logged-in Chrome session. Us... It is an AI Agent Skill for Claude Code / OpenClaw, with 86 downloads so far.
How do I install weread_assitant?
Run "/install weread-assitant" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is weread_assitant free?
Yes, weread_assitant is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does weread_assitant support?
weread_assitant is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created weread_assitant?
It is built and maintained by MingChaoXu (@mingchaoxu); the current version is v1.0.1.
More Skills