Wechat CLI
Read-only access to local WeChat chats through rion-wechat-cli, plus a guided...
Install
npx skills add Rion-Wu-tech/wechat-intelligence-hub --skill wechat-cli -g -a claude-code -y- Repository
- Rion-Wu-tech/wechat-intelligence-hub2.8k
- Category
- Data and ML
- Updated
- 19d ago
- License
- AGPL-3.0
- Context cost
- Mediumabout 1,800 tokens
- Runs scripts
- Yes, review before use
What it does
Read-only access to local WeChat chats through rion-wechat-cli, plus a guided first-access workflow when the user asks to connect their own account or obtain its local database keys. Use for chat search, contact history and unsent reply drafts; acquisition requires separate confirmation.
Rion WeChat CLI
Use rion-wechat-cli as the single public interface for local, read-only WeChat evidence. The public package must use Rion's independently implemented Reader by default and must not silently discover or invoke an old wechat-cli installation.
Default public entrypoint:
"${CODEX_HOME:-$HOME/.codex}/skills/wechat-cli/scripts/reader.sh" <command> <args>
An independently installed compatible CLI may be selected only when the user explicitly sets RION_WECHAT_CLI_BIN (legacy RION_WECHAT_READER_BIN remains accepted). Never describe notification-only coverage as complete chat access.
Core workflow
For key/import failures, prefer scripts/access.sh diagnose (helper revision 2026-09-22.1+). With an explicitly supplied --source and --database-root, it checks material in a disposable configuration without replacing an active setup. Preserve material_error.code: JSON encoding, raw-key format, salt mismatch, dependencies and schema support are different failures. --jev-request only prepares an allowlisted offline request; it never calls an API. External classification cannot establish valid keys or authorize acquisition. See diagnosis upgrades.
For Windows access feedback or onboarding, read Windows staged access. A community success report is not an integrated provider or authorization to run attached code. Diagnose dependencies, actual DLL identity, material conversion and ACLs separately; do not bypass platform checks or repeat macOS acquisition on Windows.
