slack-reader

Fetch Slack messages by permalink and resolve user mentions into structured JSON.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/SuperCorks/agent-skills --skill slack-reader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slack-reader
Source: https://github.com/SuperCorks/agent-skills/tree/main/slack-reader
Command: npx skills add https://github.com/SuperCorks/agent-skills --skill slack-reader

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @slack/web-api, and includes scripts (resource) components.

What problem does it solve?

Teams often need to fetch a specific Slack message directly from a permalink and view its full context—content, thread replies, and channel metadata—without granting broad access to the workspace data.

Core Features & Use Cases

  • Read a message by permalink and resolve user mentions to friendly names.
  • Retrieve thread replies (if the message is a thread parent) and surrounding channel context for auditing, incident review, or knowledge capture.
  • Provide channel metadata (name, topic, purpose) and user profiles, with multi-workspace support and read-only access.
  • Use case: an engineering incident review uses a single command to pull the exact message, its related replies, and relevant context for documentation.

Quick Start

Run the Slack Reader to fetch a message by permalink: node scripts/read-message.js --url "<permalink>" [--workspace <alias>] [--context-size <n>]

Frequently Asked Questions about slack-reader

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

FAQPage Schema
How do I read a Slack message by permalink and retrieve its thread context?

You can fetch a Slack message by permalink using a Node.js script that parses the URL and calls the Slack web API. It returns a structured JSON object containing the message content, resolved user mentions, thread replies, and channel metadata.

Can I fetch Slack messages from multiple workspaces simultaneously?

Yes, you can fetch Slack messages across multiple workspaces by configuring the SLACK_WORKSPACES environment variable. Alternatively, you can use a single SLACK_BOT_TOKEN for a workspace and specify the target workspace alias via command line arguments.

What Slack metadata is included when fetching a message via its permalink URL?

Fetching a Slack message by permalink returns a structured JSON object with message content, thread replies, channel metadata like name and topic, and resolved user mentions. This output supports incident review and auditing without granting broad workspace access.

Do I need the Slack web API SDK to resolve user mentions from a permalink?

Yes, resolving user mentions to friendly names from a Slack permalink requires the @slack/web-api SDK. This dependency allows the script to authenticate, fetch profiles, and assemble normalized message content with read-only access.

How do I pull surrounding channel context for an engineering incident review from Slack?

You can pull surrounding channel context for an incident review by running the read script with the --context-size argument. This fetches adjacent messages alongside the permalink target to provide broader auditing and documentation context.

Does this approach require broad workspace access to retrieve a specific Slack thread?

No, retrieving a specific Slack thread by permalink does not require broad workspace access. The script operates with read-only permissions scoped to fetching the targeted message, its thread replies, and associated channel metadata.