sammielisha425-design Discord Chat Capture
Routing boundaries
Use this skill for:
- Discord Desktop remote-debug capture.
- Discord channel/thread pagination, cleanup, indexing, and summaries.
- server capture workflows.
Do not use this skill for:
- QQ chat capture -> use
qq-chat-capture. - General web/platform research -> use
agent-reach. - Codex Desktop Browser/iab or Cockpit/API repair -> use the relevant local repair skill.
Default workflow
- Use workspace:
<YOUR_CHAT_CAPTURE_WORKSPACE> - Check Discord debug endpoint:
http://127.0.0.1:<DISCORD_DEBUG_PORT>/json/list - For normal Discord thread/forum capture, prefer:
work\discord_sampler\discord_<DISCORD_SERVER_NAME>_api_all_threads_sampler.py - For currently visible channel messages, use:
work\discord_sampler\discord_<DISCORD_SERVER_NAME>_dom_sampler.py - Clean/merge with:
work\discord_sampler\discord_memory.py - Keep outputs under:
work\samples\discord\
Reference map
Read references/original.md when you need:
- exact commands;
- known paths and canonical cumulative files;
- direct thread-id fallback;
- pause-time filtering;
- SQLite schema/output rules;
- reporting format.
Safety rules
- Never print or persist Discord Authorization tokens.
- Do not use screenshot/OCR for normal capture.
- Do not restore recurring automation unless the user explicitly asks.
- Keep Discord outputs separate from QQ outputs.