AI Agent Hub
Back to skills
Group Chat Summarizer icon

Group Chat Summarizer

Knowledge Management Updated 2026.08.29

Paste the following prompt into your AI chat to install this skill:

Follow https://skillhub.cn/install/skillhub.md and install @user_dfbdc5ab/group-chat-summarizer.

About this skill

Why group chats are hard to reuse

Decisions, owners, deadlines, and risks are often scattered across hundreds of messages, making manual review slow and error-prone. This skill turns Feishu, DingTalk, WeChat Work, QQ, Discord, Slack, Teams, Telegram, plain text, CSV, or JSON chat logs into structured summaries.

How it works

It detects the platform format, parses messages, extracts topics, participants, and timeline, then generates a fixed layout: basic info, topic timeline, key decisions, action items, follow-up suggestions, and notes. It recognizes task descriptions, @owners, deadline phrases, and status signals; adds sentiment labels such as collaborative, neutral, conflict, or unresolved debate; and flags blocked work, resource constraints, missing dependencies, and other risks. Basic, standard, and detailed levels support quick catch-ups through full meeting retrospectives.

Boundaries

It only uses user-provided logs or API tokens and does not access chats independently. Edited or deleted messages may remove context; complex threaded discussions may need manual clarification. Very long messages may be truncated, sensitive logs should be handled with privacy care, and owners or dates should be verified before follow-up.

Use Cases

  • After a 300-message project chat, generate a standard summary with decisions, action items, and owners.
  • Review on-call discussions for blockers and constraints, then extract risks, debates, and follow-ups.
  • Convert a Slack JSON export into an English summary with topic timeline and sentiment labels.
  • Summarize long chats by time periods, then verify owners, deadlines, and status fields.

Best For

  • Project managers: recover decisions, owners, deadlines, and blockers from post-meeting chats.
  • Knowledge managers: turn Feishu, DingTalk, or QQ logs into searchable topic summaries.
  • Engineering leads: review cross-team discussions for unresolved debates, dependencies, and conflict signals.
  • Community operators: organize discussion threads and extract key information plus follow-up suggestions.