sammielisha425-design QQ Chat Capture
Routing boundaries
Use this skill for:
- QQ group chat capture from QQNT + LiteLoaderQQNT + LLOneBot.
- Manual or incremental pull since pause time.
- QQ output indexing, summarizing, and organization.
Do not use this skill for:
- Discord capture -> use
discord-chat-capture. - Route-only QQ/微信/飞书 forwarding -> use
hermes-message-router. - Codex Desktop/Cockpit/API repair -> use the relevant local repair skill.
Default workflow
- Use workspace:
<YOUR_CHAT_CAPTURE_WORKSPACE> - Check pause state:
work\samples\manual_pause_state.json - Check OneBot:
ws://127.0.0.1:<ONEBOT_WS_PORT> - For normal manual capture, run from workspace:
python work\qq_tech_sampler\onebot_sampler.py --config work\qq_tech_sampler\config.increment.tmp.yaml sample - Re-index:
python work\qq_tech_sampler\qq_memory.py index - Keep outputs under:
work\samples\qq\
Reference map
Read references/original.md when you need:
- exact health checks;
- known groups;
- pause/stop JSON shape;
- per-group and merged output paths;
- deduplication and SQLite rules;
- reporting format.
Safety rules
- Do not uninstall QQ, LiteLoaderQQNT, or LLOneBot.
- Do not restore recurring automation unless the user explicitly asks.
- Do not start duplicate long-running samplers.
- Keep QQ outputs separate from Discord/other platforms.