gather-slack

Name: gather-slack
Availability: InStock
Author: Corca

Export Slack threads into local Markdown artifacts with attachments and user metadata.

9|3|Updated Apr 9, 2026

Search Tags:#automation #markdown #runtime #provenance #slack #artifact #thread-export

Ready to run

npx skills add https://github.com/corca-ai/charness --skill gather-slack

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gather-slack
Source: https://github.com/corca-ai/charness/tree/main/plugins/charness/support/gather-slack
Command: npx skills add https://github.com/corca-ai/charness --skill gather-slack

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Slack threads are transformed into durable local Markdown artifacts for archival and knowledge capture, so teams can reference conversations without requiring each consumer repo to re-create Slack export tooling.

Core Features & Use Cases

Automatically export thread content, user metadata, and attachments into a markdown artifact with provenance.
Preserve links, user names, and attachments to facilitate knowledge sharing across repos and teams.
Use cases include archiving important discussions, documenting decisions, and building searchable knowledge bases from Slack threads.

Quick Start

Run the Slack thread export wrapper to create a local Markdown artifact from a thread URL by providing the URL, an output path, and a descriptive title.

Frequently Asked Questions about gather-slack

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

FAQPage Schema

How do I export Slack threads to Markdown for archival?▼

Yes, you can export Slack thread attachments alongside messages to Markdown. The tool downloads attachments locally and preserves user names, links, and provenance to ensure conversations remain fully accessible in repository workflows.

What do I need to set up to export Slack messages to a local repository?▼

To export Slack messages locally, you need a Node.js runtime, a Slack token configured in your environment, and optional host-based runtime grants. User resolution caching is utilized to streamline the process across multiple exports.

Why should I convert Slack conversations into Markdown artifacts instead of keeping them in Slack?▼

Converting Slack conversations into Markdown artifacts creates persistent records that do not require each consumer repository to re-create Slack export tooling. This enables reliable knowledge capture, decision documentation, and searchable archives across teams.

Can I automate Slack thread exports for documentation purposes?▼

You can automate Slack thread exports by running the export wrapper with a thread URL, output path, and descriptive title. This generates a Markdown artifact with provenance suitable for building searchable knowledge bases and documenting decisions.

Does this Slack thread export approach work without installing dependencies in every repository?▼

This approach works without installing export tooling in every repository by generating standalone Markdown artifacts. Once the thread is exported locally with its attachments and metadata, any repository can reference the durable Markdown file directly.