Connect Apps with Composio
ComposioHQ/awesome-claude-skills
Connects an agent to 1000+ external apps through the Composio Tool Router plugin, so it can actually send emails, create issues and post messages instead of only drafting them.
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.
Install Sred Work Summary
$ npx skills add getsentry/skills --skill sred-work-summary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install getsentry/skills sred-work-summary --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sred-work-summary .claude/skills/sred-work-summary && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "sred-work-summary" agent skill from https://github.com/getsentry/skills/tree/main/skills/sred-work-summary into .claude/skills/sred-work-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sred-work-summary", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/getsentry/skills/tree/main/skills/sred-work-summaryType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add getsentry/skills --skill sred-work-summary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install getsentry/skills sred-work-summary --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/sred-work-summary .agents/skills/sred-work-summary && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sred-work-summary" agent skill from https://github.com/getsentry/skills/tree/main/skills/sred-work-summary into .agents/skills/sred-work-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sred-work-summary", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add getsentry/skills --skill sred-work-summary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install getsentry/skills sred-work-summary --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/sred-work-summary .cursor/skills/sred-work-summary && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sred-work-summary" agent skill from https://github.com/getsentry/skills/tree/main/skills/sred-work-summary into .cursor/skills/sred-work-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sred-work-summary", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/getsentry/skills.git --path skills/sred-work-summary--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add getsentry/skills --skill sred-work-summary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install getsentry/skills sred-work-summary --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/sred-work-summary .gemini/skills/sred-work-summary && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sred-work-summary" agent skill from https://github.com/getsentry/skills/tree/main/skills/sred-work-summary into .gemini/skills/sred-work-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sred-work-summary", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install getsentry/skills sred-work-summaryInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add getsentry/skills --skill sred-work-summary -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/sred-work-summary .github/skills/sred-work-summary && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sred-work-summary" agent skill from https://github.com/getsentry/skills/tree/main/skills/sred-work-summary into .github/skills/sred-work-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sred-work-summary", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add getsentry/skills --skill sred-work-summary -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install getsentry/skills sred-work-summary --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/sred-work-summary .opencode/skills/sred-work-summary && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sred-work-summary" agent skill from https://github.com/getsentry/skills/tree/main/skills/sred-work-summary into .opencode/skills/sred-work-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sred-work-summary", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
sred-work-summary- GitHub stars
- 1k
- Used in
- 3 other repos
- Token cost
- ~1.4k tokens
- SKILL.md length
- 828 words
- Files
- 1
- Skills in repo
- 27
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
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.
- Works in 8 steps: Step 1 → Step 2 → Step 3 → …
- Tasks that involve Time tracking and reporting
- SKILL.md covers Prerequisites, Process and Resources
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Sred Work Summary is an agent skill from getsentry/skills, published by the product's own GitHub organization. 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.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Productivity & Automation, covering Time tracking and reporting. It works with Notion and GitHub. The repository describes itself as: Agent Skills used by the Sentry team for development. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Time tracking and reporting
Example prompts
- “/sred-work-summary”
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit d18b7aa. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
notion.so
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Sred Work Summary loads about 1.4k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 828 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from getsentry/skills at commit d18b7aa, republished under its Apache-2.0 licence (© getsentry). 828 words, ~1,377 tokens.
Download SKILL.mdSave it as
.claude/skills/sred-work-summary/SKILL.md (or your agent's skills folder).- name
- sred-work-summary
- description
- 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.
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.
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 +%YThe 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$//' | sortEnsure:
- All the repositories listed are in the
getsentryGithub 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.
Show full SKILL.md (306 more words)Show less
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]
- [link] - [Creation date]
### Linear Tickets [X]
- [link] - [Creation date]For Github PRs, use both the title of the PR and the description of the PR for grouping. For Notion documents, use the full document for grouping. For Linear tickets use the title of the ticket and the description of the ticket.
Ensure:
- All the links in the file are assigned to a project.
- The file follows the format specified above.
- 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 7
Search for notion documents created by the "other users". Take any that are relevant to the projects in the Work Summary and add links to those Notion documents into the Work Summary in the appropriate project.
Step 8
Return a link to the Work Summary Notion doc to the user.
Ensure:
- The actual Notion document link is in the final output.
Resources
This is an example Working Summary document for the year 2025: https://www.notion.so/sentry/Work-Summary-Feb-2025-Jan-2026-3068b10e4b5d81d3a40cfa6ad3fe1078?source=copy_link
© getsentry, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/sred-work-summary of getsentry/skills.
Open the folder on GitHubat commit d18b7aa
Used in 3 other repositories
We found 12 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in getsentry/skills, which our catalogue first saw on October 7, 2026.
- sickn33/agentic-awesome-skillsskills/sred-work-summaryplugins/agentic-awesome-skills/skills/sred-work-summary+1 more
- lingxling/awesome-skills-cnantigravity-awesome-skills/skills/sred-work-summaryantigravity-awesome-skills/plugins/agentic-awesome-skills/skills/sred-work-summary+1 more
- henryalouf/ruflow.agents/skills/sred-work-summary.agents/skills/antigravity-awesome-skills/skills/sred-work-summary+4 more
Compare with similar skills
Sred Work Summary next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sred Work Summary this skillgetsentry/skills | 1k | 3 repos | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Connect Apps with ComposioComposioHQ/awesome-claude-skills | 77k | 3 repos | ~557 | Automated safety check: Pass | None | |
| Composio Cloud Toolsquarqlabs/argus | 277 | — | ~543 | Automated safety check: Pass | Apache-2.0 | |
| ClawdiClawdi-AI/clawdi | 103 | — | ~4.8k | Automated safety check: Notes | MIT | |
| ClawdiClawdi-AI/clawdi | 103 | — | ~4k | Automated safety check: Notes | MIT | |
| ConnectComposioHQ/awesome-claude-skills | 77k | 3 repos | ~987 | Automated safety check: Pass | None |
Similar skills
Composio Cloud Tools
quarqlabs/argus
Routes requests to external SaaS apps such as GitHub, Gmail, Google Calendar, Slack, Notion and Linear through cloud tools, with safeguards on irreversible actions.
Clawdi
Clawdi-AI/clawdi
API keys, tokens, memory, sessions, Projects, integrations. An agent skill from Clawdi-AI/clawdi.
Clawdi
Clawdi-AI/clawdi
API keys, tokens, memory, sessions, Projects, integrations. An agent skill from Clawdi-AI/clawdi.
Connect
ComposioHQ/awesome-claude-skills
Connect Claude to any app. An agent skill from ComposioHQ/awesome-claude-skills.
Composio
ComposioHQ/composio
Route and complete Composio work across Composio For You and Composio Platform.
More from getsentry/skills
All 27 skills in this repo- Official
Gh Review Requests
getsentry/skills
Fetch unread GitHub notifications for open PRs where review is requested from a specified team or opened by a team member.
- Official
Skill Scanner
getsentry/skills
Scan agent skills for security issues. An agent skill from getsentry/skills.
- Official
Security Review
getsentry/skills
Security code review for vulnerabilities. An agent skill from getsentry/skills.
- Official
Skill Writer
getsentry/skills
Create, synthesize, and iteratively improve agent skills following the Agent Skills specification.
- Official
Django Access Review
getsentry/skills
Django access control and IDOR security review. An agent skill from getsentry/skills.
- Official
Gha Security Review
getsentry/skills
GitHub Actions security review for workflow exploitation vulnerabilities.
Related
Categories
Questions about Sred Work Summary
What does Sred Work Summary do?
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. Sred Work Summary is an agent skill from getsentry/skills, published by the product's own GitHub organization. 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.
When should I use Sred Work Summary?
Sred Work Summary fits situations like: tasks that involve Time tracking and reporting.
How do I install Sred Work Summary in Claude Code?
Run `npx skills add getsentry/skills --skill sred-work-summary -a claude-code`. Or copy the skill folder (skills/sred-work-summary in getsentry/skills) into .claude/skills/sred-work-summary in your project. Claude Code loads it when a task matches its description.
How do I install Sred Work Summary in Codex?
Run `npx skills add getsentry/skills --skill sred-work-summary -a codex`. Or copy the skill folder (skills/sred-work-summary in getsentry/skills) into .agents/skills/sred-work-summary in your project. Codex loads it when a task matches its description.
Can I use Sred Work Summary in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add getsentry/skills --skill sred-work-summary -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sred-work-summary, .gemini/skills/sred-work-summary, .github/skills/sred-work-summary and .opencode/skills/sred-work-summary in your project.
What does Sred Work Summary need to run?
SKILL.md names no scripts, command-line tools or credentials: Sred Work Summary is instructions for the agent only.
Does Sred Work Summary access the network?
SKILL.md names 1 domain. As links in the text: notion.so. This is read from the text; nothing was executed.
Is Sred Work Summary safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Sred Work Summary use?
Sred Work Summary is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Sred Work Summary use?
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Sred Work Summary?
Skills that share tags, products or a category with Sred Work Summary: Connect Apps with Composio (ComposioHQ/awesome-claude-skills, 77k stars), Composio Cloud Tools (quarqlabs/argus, 277 stars), Clawdi (Clawdi-AI/clawdi, 103 stars) and Clawdi (Clawdi-AI/clawdi, 103 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sred Work Summary?
getsentry (a GitHub organization, an official publisher) maintains it in getsentry/skills, which has 1,038 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on October 2, 2026.
Source: getsentry/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.