wiki-fetch-slack

You can automatically sync Slack messages by configuring the Skill to fetch channel threads and direct messages, which it then formats as Markdown files and writes to your knowledge base's raw/slack directory for long-term retention.

You can filter Slack noise when archiving threads by using the default signal mode to exclude status updates and join notices, or apply a custom topic-specific inclusion filter to ingest only relevant discussions.

Yes, you can fetch Slack messages from a specific time window like the last 30 days. The Skill supports configurable fetch time windows for both public Slack channels and direct messages to retrieve historical conversations.

Yes, Slack message ingestion supports incremental fetching to avoid duplicates. The Skill utilizes cached state to track previous operations and logs them automatically to wiki/log.jsonl, ensuring only new messages are processed.

The best way to archive direct messages and channel threads as Markdown is using an automated ingestion workflow that formats Slack conversations directly into files, ensuring error-free cross-referencing with your existing work notes.

You should use full capture mode instead of signal mode for Slack archival when you need to record every message without exclusions. Switch to the all mode to bypass noise filtering and capture status updates alongside regular conversations.