slack-waterlinelisted

# Slack waterline Reads a Slack workspace the way a person would if they had the time: every channel, every DM, every thread reply, the pinned messages, the attachments, and the Google Sheets people keep linking. Then it records exactly what was read — and only what was read — so the next run starts where this one stopped. **The waterline is the line below which nothing can be missed.** Everything in this skill exists to keep that line honest. ## The one rule > **A read receipt may only describe what was DELIVERED, never what EXISTS.** Fetching is not reading. If a payload was built but nobody looked at it, it is not read, and recording it as read does not lose a message temporarily — it loses it permanently, because the next run has nothing left to find. Everything below follows from that. --- ## Setting up from zero If anything is unconfigured — no workspace, no token, missing scopes — **run the doctor first and follow what it says.** Do not guess at the state. ```bash cd skills/slack-waterline/scripts node setup.mjs # or --workspace acme ``` It checks Node, the workspace, the token, every scope, and whether anything has been read, then stops at the first real blocker and prints the exact command or click that clears it. Run it again after each fix. Full walkthrough in `references/setup.md`. The normal sequence for a brand-new workspace: ```bash node init.mjs --workspace acme --dir /path/to/acme-slack-archive node setup.mjs --workspace ac