Skip to content
Skillpedia
Documentation48k · #4238

sred-work-summary

Lets your agent review past work and create a summary. It groups project links into a document for easy organization.

What it does

This tool organizes your past year's work. It gathers links from code (GitHub), notes (Notion), and tasks (Linear) into projects and creates a Notion document with everything.

When to use it

  • ✓Need to gather a year's worth of work for report preparation.
  • ✓Want to organize notes and tasks before describing specific projects.
  • ✓Need an easy way to collect information from GitHub, Notion, and Linear for a specific period.

Example of what to ask your AI

“Create a summary of my work from the past year, grouping my GitHub PRs, Notion documents, and Linear tickets into projects.”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/sred-work-summary/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/sred-work-summary/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The tool collects your code links, notes, and tasks from the past year. It then groups these links by project and puts everything into a private Notion document, giving you the link to it.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add sickn33/agentic-awesome-skills --skill sred-work-summary

Or download just the file:

curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/sred-work-summary/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

SRED Work Summary

Collect all the Github PRs, Notion docs and Linear tickets a person completed in a given year. Group the links from all of those into projects. Put everything into a private Notion document and return a link to that document.

When to Use

  • You need to gather a year's worth of PRs, Notion docs, and Linear tickets into project groupings for SRED preparation.
  • The task is to build the upstream Notion work summary before writing individual SRED project descriptions.
  • You need a repeatable collection workflow across GitHub, Notion, and Linear for a fixed time window.

Prerequisites

Before starting make sure that Github, Notion and Linear can be accessed. Notion and Linear should be connected using an MCP. Github can be connected with an MCP, but if you have access to the gh CLI tool, you can use that instead.

If any of these can't be accessed, prompt the user to grant access before proceeding.

Process

Step 1

# Get the current year
date +%Y

The output of this command is the current year. The current year minus one is the previous year.

Step 2

Collect all of the required information from the user:

Github Username: What is the github username of the user?

Github Repositories: Which Github repositories should be searched for PRs?

The user can either specify a comma separated list, or provide a directory that contains repositories. In the second case use this command in the specified directory:

# Find github repos
find . -maxdepth 2 -name ".git" -type d | sed 's/\/.git$//' | sort

Ensure:

  • All the repositories listed are in the getsentry Github organization.

The output of this is hereafter referred to as the "user repos".

Incidents: Ask if the user wants to include incident documents.

The answer is either yes or no. If the answer is no, that will exclude certain documents from the search later on.

Other Users: Ask if there are any other users who might have created Notion documents.

This should be a comma separated list of names. Remember this as the "other users".

Step 3

Create a private Notion document entitled "SRED Work Summary [current year]". This document will be referred to as the Work Summary.

If a document with this name already exists, notify the user to rename the existing document and stop executing.

Ensure:

  • If the Work Summary already exists, stop execution.

Step 4

The time window is Feb. 1 of the previous year until Jan. 31 of the current year Find all Github PRs created by the given github username in the time window for the user repos. If the user does not want to include incident documents, ignore any Github PRs with INC-X, inc-X in the title or description. Use either the Github MCP or the gh command to do this.

Find all the Notion documents the user created in the time window. If the user does not want to include incident documents, ignore any Notion Documents with INC-XXXX in the title. Use the Notion MCP to do this.

Find all the Linear tickets the user was assigned in the time window. If the user does not want to include incident documents, ignore any Linear tickets with INC-XXXX in the title. Use the Linear MCP to do this.

Ensure:

  • All the Github PRs were created or merged in the time window and was opened by the user.
  • All the Notion docs were created in the time window and were created by the user.
  • All the Linear tickets were opened or completed in the time window and were assigned to the user when they were completed.

Step 5

For each of the Github PRs, Notion documents and Linear tickets found in Step 4, put a link into the private document created in Step 3.

Ensure:

  • There is a link for all the Github PRs in the Work Summary
  • There is a link for all the Notion docs in the Work Summary
  • There is a link for all the Linear tickets in the Work Summary
  • DO NOT truncate the lists of links. DO NOT use shorteners like "...and 75 more". Make sure that the full set of all Github PRs, Notion documents and Linear tickets is visible in the document.

Step 6

Use your own intelligence to group all the Github, Notion and Linear ticket links in the Work Summary document into projects. The format of this document is shown below.

# Projects

## [Project Name]
*Summary*: [X] PRs, [X] Notion docs, [X] Linear tickets

### Pull Requests [X]
*[repository name]
[Links to all the PRs]
- [link] - [Merge date]

### Notion Docs [X]
[Links to all the Notion docs]

…
FAQ

What is SRED?

SRED stands for Scientific Research and Experimental Development. This summary helps document the work done for projects that might qualify for tax credits.

Do I need to have Notion, GitHub, and Linear connected?

Yes, the tool needs access to these platforms. This is usually done through a connection called MCP. If you use the `gh` tool on GitHub, that can also work.

What happens if a document with the same name already exists?

The tool will notify you to rename the existing document before proceeding, to avoid conflicts.

Details

Original description by the author

Go back through the previous year of work and create a Notion doc that groups relevant links into projects that can then be documented as SRED projects.

repo: sickn33/agentic-awesome-skills

Popularity

GitHub stars
48k
Ranking position
#4238
License
MIT
Updated
10/15/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills