About this skill

Problem

WeCom group threads mix discussions, decisions, task assignments, and incident reports across a long message stream. During project reviews, manually scanning the group, filtering owners, and finding deadlines can easily miss key actions.

How It Works

This skill processes group chat text with a structured workflow:
- Parameters: captures group name, time range, and report format; defaults to the last 3 days.
- Message retrieval: matches the target group from the WeCom session list, fetches group messages where chat_type=2, and splits ranges over 500 messages into 24-hour batches.
- Cleaning: filters pure emojis, system notifications, and recalled messages, keeping substantive text.
- Four-part analysis: summarizes work topics, extracts key items and todos, and identifies recurring or high-frequency issues.
- Report output: generates a Markdown or HTML report saved as GroupSummary__.md or .html.

Boundaries

It mainly analyzes text visible to the current user; images, files, and voice messages are not processed by default and require separate download. WeCom API limits may require splitting long query ranges. Reports containing HR, finance, or other sensitive content should be shared carefully.

Screenshots

Use Cases

A project lead consolidates daily group discussions to extract decisions, incidents, and todos.
An on-call engineer reviews a week of group messages to surface recurring access-control issues.
An operations manager turns customer-group feedback into a Markdown weekly report.
A team manager pulls explicit assignments and deadlines from group chat to complete action items.

Best For

Project group leads who want traceable work summaries from group messages
On-call or ops engineers reviewing incident reports and recurring issues in chat
Operations managers converting customer-group feedback into structured weekly reports
Project managers extracting todos, owners, and deadlines from group discussions