slack

Automate Slack unread checks and conversation extraction via browser sessions.

63|12|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/iBz-04/gloamy --skill slack-ibz-04
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slack
Source: https://github.com/iBz-04/gloamy/tree/main/.agents/skills/slack
Command: npx skills add https://github.com/iBz-04/gloamy --skill slack-ibz-04

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Slack browsing and repetitive message workflows become slow and error-prone when you must manually check unread channels, search conversations, and extract details.

Core Features & Use Cases

  • Browser-based Slack automation: Navigate Slack and perform actions through an existing logged-in browser session.
  • Unread discovery & overview: Check Activity, DMs, and sidebar “More unreads” to compile what needs attention.
  • Search and extraction workflows: Use Slack’s search UI to find messages by keywords and extract visible conversation data.
  • Evidence capture: Take screenshots and annotated screenshots to document findings.

Quick Start

Connect to an existing Slack browser session on port 9222, then take a snapshot to reveal clickable refs and extract unread information.

Frequently Asked Questions about slack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Slack message extraction without an API token?

You can automate Slack message extraction without an API token by driving an existing logged-in browser session via Chrome DevTools. This Skill uses deterministic UI interactions like snapshot and click commands to navigate Slack and extract visible conversation data.

Can I monitor unread Slack channels using browser automation?

Yes, you can monitor unread Slack channels using browser automation. The Skill navigates the sidebar and Activity sections to compile unread messages across DMs and channels, relying on snapshot commands to identify what needs attention.

How do I capture Slack conversation screenshots for evidence?

To capture Slack conversation screenshots for evidence, the Skill uses browser automation commands to take screenshots of visible data. It navigates to specific channels or search results and captures the interface directly through the connected browser session.

Do I need a connected Chrome DevTools session to search Slack conversations?

Yes, you need an interactive Chrome DevTools session to search Slack conversations with this Skill. It requires connecting to an existing browser port, such as 9222, to perform deterministic UI interactions like fill and wait commands on Slack's search UI.

What are the limitations of using browser automation for Slack workspace tasks?

Limitations of using browser automation for Slack workspace tasks include dependency on a live, logged-in browser session and deterministic UI interactions. It does not use Slack APIs, meaning workflows are constrained by visible interface elements and require active browser connectivity.