polym-slack-digest

Generate daily Slack intelligence digests and publish them to Feishu docs.

8|Updated May 13, 2026
One-click install
npx skills add https://github.com/byteplus-sa/polym --skill polym-slack-digest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: polym-slack-digest
Source: https://github.com/byteplus-sa/polym/tree/main/skills/polym-slack-digest
Command: npx skills add https://github.com/byteplus-sa/polym --skill polym-slack-digest

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Slack daily digesting turns dispersed channel conversations into a structured, decision-ready intelligence feed, so teams don’t waste time manually scanning messages.

Core Features & Use Cases

  • Slack → Feishu digest publishing: generates per-day digest docs with executive summary, highlights, TODO backlog, pipeline, risks, and by-channel verbatim transcripts, then pins entries into a single newest-on-top index doc.
  • Twice-daily automated runs with watchdog: runs at configured slots and verifies the digest sections exist 20 minutes later, automatically retrying with backoff until success.
  • Owner detection and stakeholder routing: resolves Slack users, replaces mentions with names, and identifies BytePlus/ByteDance owners per channel to drive actionable next steps.

Quick Start

Tell the agent: set up Slack daily digest, then follow the onboarding prompts to configure your Slack OAuth token and your Lark bot credentials so it can create the index doc and schedule daily digests.

Frequently Asked Questions about polym-slack-digest

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

FAQPage Schema
How do I automate Slack channel summarization into daily Feishu digests?

To automate Slack summarization into Feishu digests, a pipeline extracts channel history, generates AI-synthesized executive summaries, highlights, and TODO backlogs, then pins them as newest-on-top entries in a durable Lark docs index.

What is the best way to schedule recurring Slack to Lark docs reporting workflows?

The best way to schedule recurring Slack to Lark reporting workflows is using durable host UI routines for production scheduling, avoiding local OS schedulers, with a watchdog that verifies digest sections 20 minutes post-run and retries with backoff until success.

Can I use Slack OAuth tokens and Lark bot credentials to publish channel transcripts to Feishu?

Yes, you can use Slack OAuth tokens and Lark bot credentials to publish channel transcripts to Feishu. The onboarding process persists these credentials to authenticate API access for creating index docs and routing stakeholder notifications.

Does Slack to Feishu digest publishing support owner detection and stakeholder routing?

Slack to Feishu digest publishing supports owner detection by resolving Slack users, replacing mentions with names, and identifying channel owners to drive actionable next steps within the generated intelligence feed and stakeholder routing.

Why does my Slack digest pipeline fail to create durable scheduling without credential persistence?

Your Slack digest pipeline fails because it requires a SKILL-driven pipeline that persists credentials and routine state to enforce hard digest template rules, update the index with de-duplication, and escalate or stop on durable-scheduling or credential failures.