telegram-summarize: Skill for Claude Code

Meeting Minutes Skill — Short Internal Meetings

Purpose / Overview

This Skill produces high-quality, consistent meeting minutes for internal meetings that are 60 minutes or shorter. Output is designed to be clear, actionable, and easy to convert into task trackers (e.g., GitHub Issues, Jira). The generated minutes prioritize decisions and action items so teams can move quickly from discussion to execution.

Telegram Discussion Summary Mode

Use this mode when the source is a Telegram channel or group. It replaces the meeting-specific intake questions and the Strict Minutes Schema below: do not ask for an organizer, agenda, reviewer, action items, or a next meeting unless the Telegram messages themselves establish them.

The core unit of the summary is a topic with its participants, positions, humor, and resources kept together. This preserves the social context of the discussion instead of reducing it to an anonymous list of conclusions.

Topic block

Use this shape for every substantive topic:

### <Topic>

- **What was discussed:** <concise synthesis>
- **Active participants and positions:**
  - @handle — <main claims, arguments, examples, or disagreement>
- **Outcome / disagreement:** <supported conclusion or unresolved split>
- **Resources:**
  - <exact URL> — <why it mattered in this topic> — <source message link>
- **From the chat:**
  > "<verbatim joke or meme quote>" — @handle, <reaction count>, <source message link>

Apply these rules:

1. Attribute every topic. Name the people who materially advanced that topic and summarize the main thought each person contributed. Message volume alone does not make someone an active participant. A global participant table may supplement this, but never replace topic-level attribution.
2. Use humor as evidence of the chat's tone. Quote a topical joke or meme verbatim when it naturally fits the topic. A context-free joke may appear in a separate From the chat interlude only when verified reaction metadata totals more than 4 reactions. Prefer the strongest 1–3 quotes across the whole summary so humor adds texture without taking over.
3. Never infer reactions. Show a reaction count only when the source payload provides it. If reaction metadata is unavailable, do not claim that a quote passed the reaction threshold and do not use it as a context-free interlude.
4. Keep resources with their discussion. Place GitHub repositories, documentation, articles, tools, videos, and other links inside the topic where they were mentioned. Preserve URLs exactly and add the source Telegram message link when possible.
5. Reserve a standalone resources section for orphan links. Use Standalone resources only for links posted without enough surrounding discussion to assign them to a topic. Do not duplicate topic resources there.
6. Preserve quotation fidelity. Do not rewrite, correct, sanitize, or merge a quoted joke. Keep it short, identify the author, and link the source message when possible.