slack-kb-individual

Extract Slack threads by user within a date window to JSONL.

5|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/tomzx/agents --skill slack-kb-individual
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slack-kb-individual
Source: https://github.com/tomzx/agents/tree/main/skills/slack-kb-individual
Command: npx skills add https://github.com/tomzx/agents --skill slack-kb-individual

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, python-dotenv.

What problem does it solve?

Collect all Slack conversations a specific person participated in during a date range, enabling performance reviews, 1:1 prep, or building a picture of someone's contributions. Outputs JSONL via the Slack API.

Core Features & Use Cases

  • Deduplicate and aggregate: search across Slack to identify unique threads a user participated in.
  • Enrich with context: resolve channel names and per-message user names, and output thread previews and permalink.
  • Use cases: performance reviews, knowledge consolidation, or preparing for 1:1s.

Quick Start

Run the tool with --user and --after/--before, then save results to a file with -o.

Frequently Asked Questions about slack-kb-individual

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

FAQPage Schema
How do I collect all Slack threads started by a specific user within a date range?

To collect Slack threads by user and date, scan Slack messages, deduplicate by thread, and fetch thread roots. The tool outputs JSONL files containing thread timestamps, channel names, replies, previews, and permalinks for performance reviews or 1:1 preparation.

What Slack API credentials do I need to extract conversation threads to JSONL?

Extracting Slack conversation threads to JSONL requires a SLACK_TOKEN and SLACK_COOKIE stored in a local .env file. These credentials authenticate the requests library to access the Slack API for scanning messages and resolving channel names.

Can I run Slack data collection in parallel to speed up thread extraction for performance reviews?

Yes, Slack thread extraction supports multiple workers to run data collection in parallel. This parallel processing accelerates scanning messages and aggregating unique threads across channels when preparing performance review data.

How does thread deduplication work when searching Slack conversations for a specific user?

Thread deduplication works by scanning Slack messages for a specific user, identifying unique thread roots, and fetching each root only once. This prevents duplicate entries in the JSONL output when a user participated in the same thread multiple times.

What metadata is included in the JSONL output when extracting Slack user threads?

The JSONL output includes thread_ts, channel, channelName, replies, preview, and permalink for each extracted Slack thread. This enriched context resolves channel names and per-message user identities for knowledge consolidation and review preparation.