end-of-week-summary

Summarize weekly Slack activity and contributions into a Markdown digest.

5|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/tomzx/agents --skill end-of-week-summary
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: end-of-week-summary
Source: https://github.com/tomzx/agents/tree/main/skills/end-of-week-summary
Command: npx skills add https://github.com/tomzx/agents --skill end-of-week-summary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of a concise weekly digest that captures Slack activity, colleague contributions, outstanding action items, and expressions of thanks.

Core Features & Use Cases

  • Summarizes personal Slack activity for the week and compiles individual contributions.
  • Aggregates colleague activity across channels to highlight collaboration.
  • Collects outstanding action items and formal appreciation into a single digest.
  • Outputs a Markdown summary suitable for sharing with the team or leadership.

Quick Start

Run the end-of-week-summary skill to generate the weekly digest from your Slack notes and team activity.

Frequently Asked Questions about end-of-week-summary

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

FAQPage Schema
How do I generate a weekly Slack digest from my daily notes?▼

To generate a weekly Slack digest, the skill aggregates daily .slack.md files stored in your NOTES_DIR, processing colleague contributions in parallel to output a concise markdown summary.

Can I compile Slack action items and team contributions into a single weekly report?▼

Yes, compiling Slack action items and team contributions into a single weekly report is the core function, aggregating per-colleague activity and outstanding tasks into a structured markdown digest.

What is the best way to summarize weekly Slack activity for leadership?▼

Summarizing weekly Slack activity for leadership is achieved by aggregating peer contributions, outstanding action items, and thanks into a reproducible markdown briefing organized by year and week.

Do I need specific markdown files to summarize weekly Slack activity?▼

Yes, you need daily .slack.md notes placed inside a configured NOTES_DIR to provide the raw Slack activity data required for aggregation and summary generation.

Does this tool work for tracking individual colleague contributions across Slack channels?▼

Tracking individual colleague contributions across Slack channels is supported through parallel processing of daily notes, aggregating each peer's activity into the final weekly digest.

When should I not use an automated weekly report for Slack activity?▼

You should avoid automated weekly reporting if your team's Slack activity is not captured in daily .slack.md notes, as the skill relies entirely on this pre-existing markdown data structure.