Ingest Slack Thread

Parse Slack thread exports into structured product context documents.

14|2|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/rchandnaWUSTL/pm-digital-twin --skill ingest-slack-thread
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Ingest Slack Thread
Source: https://github.com/rchandnaWUSTL/pm-digital-twin/tree/main/skills/ingest-slack-thread
Command: npx skills add https://github.com/rchandnaWUSTL/pm-digital-twin --skill ingest-slack-thread

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill transforms raw Slack thread exports into organized product intelligence documents, making it easier to track decisions, questions, and key information from conversations.

Core Features & Use Cases

  • Parses Slack Exports: Accurately identifies messages, authors, and timestamps from typical Slack export formats.
  • Extracts Key Information: Identifies and separates key decisions made and unresolved questions raised within the thread.
  • Enriches Metadata: Automatically populates one_line_description, related_customers, and related_jira fields in the frontmatter.
  • Use Case: After a customer support or technical discussion in Slack, use this Skill to automatically create a structured document summarizing the conversation, decisions, and action items for easy reference and integration into other systems.

Quick Start

Use the ingest-slack-thread skill to process the attached slack_export.zip file.

Frequently Asked Questions about Ingest Slack Thread

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

FAQPage Schema
How do I structure Slack thread exports into organized product context documents?

To structure Slack thread exports into product context, you can parse the raw export to extract thread participants, timestamps, key decisions, and unresolved questions into a comprehensive reference document.

What is the best way to extract key decisions and unresolved questions from a Slack conversation?

Extracting key decisions and unresolved questions from Slack conversations involves parsing thread exports to identify and separate actionable outcomes, while also capturing participant details and emoji reactions for context.

Can I automatically link related customers and Jira issues when parsing Slack threads?

Yes, you can automatically link related customers and Jira issues when parsing Slack threads by enriching the document frontmatter with metadata extracted directly from the conversation content.

Does Slack thread parsing handle various timestamp formats and participant name normalization?

Slack thread parsing handles various timestamp formats and participant name normalization to ensure accurate chronological ordering and consistent identification of thread contributors across exports.

How do I process a slack_export.zip file to track product intelligence discussions?

To process a slack_export.zip file for product intelligence, attach the archive to the ingestion script to automatically transform raw support or technical discussions into structured, trackable documentation.

What are the limitations of structuring Slack threads into product context documents?

Limitations of structuring Slack threads include relying on standard export formats for accurate parsing, as complex conversational nuances or fragmented context across multiple channels may not be fully captured in the final document.