Session Summary Generator

VerifiedSafe

Generates weekly or monthly summaries from retrospectives, activity logs, learnings, and git history. Consolidates data into structured reports with metrics, accomplishments, and open items. Helps review progress and plan next steps.

Sby Skills Guide Bot
ProductivityIntermediate
6/2/2026
Claude Code
#summary#retrospective#activity-log#weekly-report#monthly-report

Recommended for

Automated summary

Generates weekly or monthly summaries from retrospectives, activity logs, and Git commits.

Strengths

  • Automates regular progress reporting
  • Aggregates multiple data sources (logs, git, learnings)
  • Produces structured Markdown files ready for version control
  • Supports historical periods for past summaries

Limitations

  • Requires retrospectives and logs to be manually maintained
  • Depends on the configured timezone (Asia/Bangkok by default)
  • Only generates text summaries, no charts or advanced metrics
When to use it

To review work accomplished each week or month and derive actionable insights.

When not to use it

For real-time analysis or reports requiring complex data visualizations.

Security analysis

Safe
Quality score90/100

The skill uses standard git and file system operations (grep, find, git log/commit) for data aggregation and reporting within the project. No destructive commands, network calls, or handling of secrets. It is a legitimate documentation generator.

No concerns found

How this analysis is made

Examples

Weekly summary for current week
/summary weekly
Monthly summary for a specific month
/summary monthly 2026-01
Weekly summary for a historical week
/summary weekly 2025-12-01

name: summary description: Generates weekly or monthly session summaries from retrospectives and activity logs. argument-hint: "[weekly|monthly]" user-invocable: true

Summary - Session Summaries

Generate weekly or monthly summaries from retrospectives, learnings, and activity logs.

Usage

/summary weekly          # Generate current week summary
/summary monthly         # Generate current month summary
/summary weekly 2026-01  # Generate for specific week/month

Output: $PROJECT_ROOT/docs/summaries/YYYY-MM-weekN.md or YYYY-MM.md

Instructions

Language Setting

Check LANGUAGE in docs/current.md. If th, translate output per references/language-guide.md. See references/bash-helpers.md for detection snippet.

1. Determine Period

Parse arguments:

  • weekly → current week (Mon-Sun)
  • monthly → current month
  • Optional date parameter for historical summaries
export TZ='Asia/Bangkok'
YEAR=$(date '+%Y')
MONTH=$(date '+%m')
WEEK=$(date '+%V')

2. Gather Data

export TZ='Asia/Bangkok'

# Activity log entries for the period
grep "^$YEAR-$MONTH" docs/logs/activity.log

# Retrospectives for the period
find docs/retrospective/$YEAR-$MONTH -name "*.md" -type f | sort

# Learnings for the period
find docs/learnings/$YEAR-$MONTH -name "*.md" -type f | sort

# Git commits for the period
git log --oneline --since="[start-date]" --until="[end-date]"

# Knowledge base updates
git log --oneline --since="[start-date]" --until="[end-date]" -- docs/knowledge-base/

3. Analyze and Generate

Read each retrospective/learning file and extract:

  • Task descriptions
  • Types (feature, bugfix, refactor, etc.)
  • Key decisions
  • Open items (unchecked checkboxes)

4. Create Summary File

Use the template below.

5. Commit

git add docs/summaries/
git commit -m "docs: [weekly|monthly] summary for [period]"

Weekly Template

# Week [N] Summary ([start-date] - [end-date])

## Overview

| Metric | Value |
|--------|-------|
| Sessions | [count] |
| Issues Closed | [count] |
| PRs Merged | [count] |
| Learnings Captured | [count] |

## Sessions

| Date | Task | Type | Status | Issue |
|------|------|------|--------|-------|
| MM-DD | [task description] | feat/fix/refactor | completed/pending | #N |

## Key Accomplishments

- [accomplishment 1]
- [accomplishment 2]

## Learnings Captured

- `docs/learnings/[path]` - [title]

## Knowledge Distilled

- `docs/knowledge-base/[topic].md` - [title]

## Decisions Made

| Decision | Context | Rationale |
|----------|---------|-----------|
| [decision] | [context] | [rationale] |

## Open Items

- [ ] [carried over items from retrospectives]

## Next Week Focus

- [suggested focus areas based on open items]

Monthly Template

# [Month Year] Summary

## Overview

| Metric | Value |
|--------|-------|
| Total Sessions | [count] |
| Issues Closed | [count] |
| PRs Merged | [count] |
| Learnings | [count] |
| Knowledge Base Updates | [count] |

## Weekly Breakdown

| Week | Sessions | Key Focus |
|------|----------|-----------|
| W1 | [count] | [focus] |
| W2 | [count] | [focus] |
| W3 | [count] | [focus] |
| W4 | [count] | [focus] |

## Top Accomplishments

1. [accomplishment]
2. [accomplishment]
3. [accomplishment]

## Patterns & Trends

- [observed pattern in work]
- [recurring themes]

## Open Items Carried Over

- [ ] [items still pending]

## Next Month Priorities

- [priority 1]
- [priority 2]

Related Commands

| Command | Purpose | |---------|---------| | /td | Create retrospective (data source) | | /mem | Capture learnings (data source) | | /consolidate | Consolidate auto-captured files | | /summary | Generate summaries (you are here) |

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/session-summary-generator-mmbizkvx/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/session-summary-generator-mmbizkvx' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/session-summary-generator-mmbizkvx/download' --output '.skill-downloads/session-summary-generator-mmbizkvx/SKILL.md.part' && mv '.skill-downloads/session-summary-generator-mmbizkvx/SKILL.md.part' '.skill-downloads/session-summary-generator-mmbizkvx/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/session-summary-generator-mmbizkvx/SKILL.md' && test -s '.skill-downloads/session-summary-generator-mmbizkvx/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/summary' && cp -R '.skill-downloads/session-summary-generator-mmbizkvx' '.claude/skills/summary'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/session-summary-generator-mmbizkvx'

openskills read 'session-summary-generator-mmbizkvx'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/session-summary-generator-mmbizkvx/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills