← Back to Skills Marketplace
272
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install slack-reader
Description
Read and summarize Slack channel history and thread conversations. Use when receiving Slack links (https://...slack.com/archives/...) or requests to view cha...
Usage Guidance
This skill will call the Slack API and requires a Slack bot token, but the registry metadata does not declare any required credentials or config paths. Before installing: (1) Inspect ~/.openclaw/openclaw.json to see whether it already holds other secrets and to confirm the skill only reads channels.slack.botToken; (2) Provide a dedicated bot token with the minimum necessary scopes (e.g., channels.history, conversations.replies, users:read) rather than a user token or a token with wide scopes; (3) Note the skill writes a cache to ~/.cache/slack-reader/users.json — consider file permissions or running in an isolated environment; (4) If you cannot verify the source, do not install system-wide; instead run the scripts in a sandbox or review the full code to ensure no hidden endpoints are contacted. The main red flag is the undocumented config file usage — ask the publisher to document credential setup or update the manifest to declare the required config/credential.
Capability Analysis
Type: OpenClaw Skill
Name: slack-reader
Version: 1.0.0
The slack-reader skill is a well-implemented tool for fetching and formatting Slack channel and thread history. It retrieves a bot token from a local config file (~/.openclaw/openclaw.json) and uses standard Python libraries (urllib) to communicate with the official Slack API. The code includes robust features like parallelized fetching, rate-limit handling, and a local user-name cache (~/.cache/slack-reader/users.json) to optimize performance. No indicators of malicious intent, data exfiltration, or harmful prompt injection were found.
Capability Assessment
Purpose & Capability
The skill's stated purpose (read/summarize Slack threads) legitimately requires access to the Slack Web API. The code fetches a Slack bot token from ~/.openclaw/openclaw.json (channels.slack.botToken). However, the registry metadata declares no required env vars or config paths. This is an incoherence: a Slack-integration skill should declare its credential requirement.
Instruction Scope
SKILL.md describes how to invoke the scripts but does not document the need to supply a bot token or the specific config file path. The runtime code reads ~/.openclaw/openclaw.json and writes a cache at ~/.cache/slack-reader/users.json. The instructions give the agent broad discretion (e.g., fetching full channel history and thread replies) but omit the credential/config requirements and where data is persisted.
Install Mechanism
There is no install spec (instruction-only), and included scripts are plain Python/Bash. No external installers or downloads are used. Risk from install mechanism is low.
Credentials
The code requires a Slack bot token stored in a local config file, which is reasonable for the functionality, but the manifest did not declare this credential or config path. The skill will fail (and exit) if the config file is missing or malformed. It also creates/updates a local cache at ~/.cache/slack-reader/users.json. Because required credentials are not declared, users may unknowingly provide a token with broader scopes or reuse a shared config containing other secrets.
Persistence & Privilege
The skill does not request always:true and does not modify other skills or system-wide settings. It persists only a local user-name cache and reads a local config file; this is within reasonable scope for a client tool but should be documented.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install slack-reader - After installation, invoke the skill by name or use
/slack-reader - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of Slack Thread Reader.
- Fetches and outputs Slack channel history, threads, and individual replies in a clean, chronological, LLM-friendly format.
- Supports three modes: channel history, full thread, and single reply (automatically determined from Slack link or arguments).
- Offers options for message limits, time range, inclusion of thread replies, thread reply limits, and output order.
- Outputs include timestamps, sender names, reactions, attachments, thread participation, and more; all formatted for easy reference and summarization.
- Provides usage guidance, output examples, and technical notes on pagination, caching, rate limiting, and error handling.
- Asks for clarification if link type and user request don't match, especially regarding whether to include thread replies.
Metadata
Frequently Asked Questions
What is Slack Thread Reader?
Read and summarize Slack channel history and thread conversations. Use when receiving Slack links (https://...slack.com/archives/...) or requests to view cha... It is an AI Agent Skill for Claude Code / OpenClaw, with 272 downloads so far.
How do I install Slack Thread Reader?
Run "/install slack-reader" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Slack Thread Reader free?
Yes, Slack Thread Reader is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Slack Thread Reader support?
Slack Thread Reader is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Slack Thread Reader?
It is built and maintained by Epikoding (@epikoding); the current version is v1.0.0.
More Skills