slack-chat

Pull unread Slack messages into a local Markdown store with YAML metadata.

Updated Jan 2, 2026
One-click install
npx skills add https://github.com/mikesmullin/slack --skill slack-chat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slack-chat
Source: https://github.com/mikesmullin/slack/tree/main
Command: npx skills add https://github.com/mikesmullin/slack --skill slack-chat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Slack inbox overload and scattered context make it hard to read, triage, and act on unread messages. This Skill provides an offline-first workflow and a command-line interface to pull unread messages, view details, resolve IDs to names, and mark items as processed, all from local storage or via Slack's API.

Core Features & Use Cases

  • Offline-first backlog management: fetch unread messages from channels, direct messages, and threads into a local Markdown store with metadata.
  • Contextual viewing and ID resolution: enrich messages with human-readable names for users and channels, and show surrounding context on demand.
  • Workflow automation: mark messages as read locally (and optionally on Slack) and support per-thread or per-channel bulk operations; resolve IDs from storage or API for quick posting and replies.

Quick Start

Install the Slack-Chat CLI, run slack-chat pull to fetch unread messages, then review with slack-chat inbox summary and mark items with slack-chat inbox read.

Frequently Asked Questions about slack-chat

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

FAQPage Schema
How do I manage an overloaded Slack inbox offline?

To manage an overloaded Slack inbox offline, you can use an offline-first CLI to pull unread messages from channels, DMs, and threads into a local Markdown store with YAML frontmatter for contextual review.

How do I triage unread Slack messages and threads from the command line?

You can triage unread Slack messages and threads from the command line by pulling unread items into a local index, viewing summaries, resolving user IDs to names, and marking items as read locally or via the Slack API.

Can I resolve Slack user and channel IDs locally without constant API calls?

Yes, you can resolve Slack user and channel IDs locally without constant API calls by using local caches that store metadata, falling back to Slack API calls only when needed to enrich messages with human-readable names.

Does this offline Slack backlog reader support bulk actions per channel or thread?

Yes, this offline Slack backlog reader supports bulk operations per channel or thread, allowing you to mark multiple messages as read locally and optionally synchronize the read status with your Slack workspace.

What is the best way to automate Slack message review and response?

The best way to automate Slack message review and response is using a CLI that fetches unread messages, indexes them with Markdown bodies and metadata, and supports workflow actions for reading and replying to items.

Do I need a live Slack connection to read and triage my pulled messages?

No, you do not need a live Slack connection to read and triage pulled messages because the system uses offline-first storage, allowing you to review and mark items locally before optionally synchronizing changes.