从 Get 笔记 (biji.com) 同步语音笔记到本地 Markdown

This skill appears to do what it says — sync biji.com (Get 笔记) notes to local Markdown — but review these operational considerations before installing or running: - Verify the network hosts: the code uses multiple domains (get-notes.luojilab.com, notes-api.biji.com, www.biji.com). Confirm these are expected (official or trusted proxies) for your account before providing interactive login. - npm / Playwright: run npm install in a controlled environment. Playwright will download browser binaries and increase the install footprint; review package.json and package-lock if you have strict supply-chain policies. - Tokens and state files: the skill stores tokens and browser storage locally in .token-cache.json and .auth-state.json. Treat these files as sensitive — store them in a secure location and avoid committing them to VCS. If you stop using the skill, delete those files to revoke persistent access. - Browser login & headless refresh: the scripts may open a real browser for manual login (interactive) or run headless to refresh tokens. Only run these actions on a machine you trust and avoid running on shared hosts. - File deletion: dedupe.js will permanently delete duplicate .md files under OUTPUT_DIR when run. Run it only after backing up your notes or testing in a copy of your notes directory. - Test first: run in a test/output directory (set OUTPUT_DIR) and use TEST_LIMIT to sync a small number of notes to confirm behavior and file formats before doing a full sync. If you want greater assurance, request confirmation from the skill author about the use of the luojilab host (if unfamiliar), or inspect network traffic during a test run to verify requests go only to expected endpoints.

Type: OpenClaw Skill Name: get-biji Version: 3.0.0 The skill is a legitimate utility designed to sync voice notes from the Get Notes service (biji.com) to local Markdown files. It employs Playwright for browser-based authentication and token management, which is a standard approach for services lacking a public API. The code logic in scripts like `api.js` and `sync.js` is transparent, directing network traffic only to official service domains (biji.com and luojilab.com) and restricting file operations to the user-defined output directory and local configuration files (.auth-state.json, .token-cache.json). No evidence of data exfiltration, malicious execution, or prompt injection was found.