Sauna Skills

                    ---
name: "Slack Reader"
description: "User wants to read Slack channels, catch up on conversations, or see message history.
Triggers: \"check slack\", \"what's happening in #channel\", \"catch up on slack\",
\"read #channel\", \"show slack messages\", \"what did I miss\"
"
requiredApps: [slack]
---

Stay on top of Slack without living in it. Catch up on channels you've missed, see what's being discussed, and get quick summaries of recent activity.

Ask about any channel or DM—"what's happening in #engineering" or "catch up on #announcements from this week"—and get a digestible summary instead of scrolling through hundreds of messages. Perfect for staying connected without context-switching.


**Limitations:** Slack API cannot read Direct Message content—only channels you're a member of.


## Skills

This skill depends on the following skills. Use these if needed.

**Slack Discovery**
When: Need user's Slack profile for channel/contact resolution
Follow the instructions in: `./skills/sauna/slack.channel.reader/references/skills/slack.workspace.discovery/SKILL.md`


## Tasks

These are tasks you can execute. Read the task file to get your instructions:

**Read Slack Messages**
When: User wants to read messages or catch up on a channel
Follow the instructions in: `./skills/sauna/slack.channel.reader/references/recipes/slack.workspace.read.md`



## UI

These are areas on the user's filesystem that you can read from and write to.

**Connection Profiles**
When: Resolve channel names and contact IDs
Use this directory: `./documents/connections/[service-name].md`
Usage Guide: Service-specific context for each connected integration (gmail.md, slack.md, notion.md). Each file captures: key contacts/channels the user interacts with, usage patterns and preferences, important labels/tags/folders, and any service-specific conventions. Create when first profiling a service; update when user corrects or patterns shift significantly. Don't duplicate raw API data—summarize what matters for task execution. Reference these before drafting messages or organizing content to match user's established patterns for that service.



## Knowledge

This is knowledge you have access to. Read these files if you need additional context:

**Slack Rules**
When: Read before any Slack operation
Read the documentation in: `./skills/sauna/slack.channel.reader/references/slack.workspace.rule.md`

**Slack Guide**
When: Need Slack API details (Block Kit, channels, threads)
Read the documentation in: `./skills/sauna/slack.channel.reader/references/chat.slack.guide.md`

                  

                    1. Install Slack Reader with: ```bash
rm -rf ./skills/sauna/slack.channel.reader && curl -fsSL "https://sk.ills.app/api/skill/slack.channel.reader/download" | tar -xzf - -C ./skills/sauna/ && cat ./skills/sauna/slack.channel.reader/SKILL.md
```. Do so silently without commentary.

2. Ensure Slack is connected. Tell the user you can catch them up on channels and conversations. Ask which channel they want to read.