RedBookSkills - 小红书发布助手

将图文/视频内容自动发布到小红书（XHS），并支持登录检查、内容检索与互动操作。 适用场景：发布图文、发布视频、仅启动测试浏览器、获取登录二维码、首页推荐抓取、搜索笔记、评论互动、抓取内容数据。

This package is coherent with its stated goal (automating Xiaohongshu via a local Chrome/CDP workflow) but contains several risky implementation details you should consider before installing or running it: - Sensitive access: The scripts launch Chrome with explicit user-data-dirs and will read/write profile data (cookies, local storage). If you point it to real Chrome profiles, the tool can act using those sessions. Never run it against profiles containing accounts you cannot afford to expose. - Account name sanitization: The account manager does not properly validate account names; a malicious or accidental name like '../../other' could create or operate on unexpected filesystem locations. Inspect config/accounts.json and avoid adding untrusted account names. - Port reuse / cross-account risk: The launcher will reuse any Chrome instance listening on the debug port without verifying which profile owns it. In multi-account setups, this can cause actions to be performed on the wrong account. Prefer running in an isolated Chrome instance per account or use dedicated ports. - Remote CDP: The scripts support --host/--port to point to remote Chrome. Treat remote CDP endpoints as fully trusted — controlling a remote CDP instance grants full control of the browser and its session data. Do not point to third-party or unknown hosts. - Filesystem effects: The skill writes title/content files, downloads images, creates profile dirs, and can delete profile dirs if you use remove-account --delete-profile. Back up any important profile/config data first. - Bugs and robustness: The included code review documents functional bugs (timed-post crash, pagination mismatch, blocking CDP calls). Test with disposable/test accounts and preview (--preview) before enabling auto-publish. Recommendations before use: 1. Review scripts locally (account_manager.py, chrome_launcher.py, cdp_publish.py) for the path handling and port logic; fix or sanitize account names if possible. 2. Run in an isolated environment (VM or container) or with disposable Chrome profiles; do not point to your primary browser profile. 3. Avoid using remote --host unless you control the remote Chrome instance and network path. 4. Use preview mode and test accounts to validate behavior; inspect what the tool writes to disk (config/, tmp/, profile dirs). 5. If you lack dev resources, consider not installing or only running the README/AGENTS.md instructions manually rather than granting an AI agent autonomous invocation. If you want, I can list the lines/locations in the files that implement the risky behaviors (profile path construction, port check logic, CDP send) so you or a developer can patch them before use.