sred-project-organizer by getsentry/skills
npx skills add https://github.com/getsentry/skills --skill sred-project-organizerSRED 期望项目以特定格式呈现。获取过去一年中已完成的项目列表,并将其总结为 SRED 期望的格式,并提供支持证据。输出一个 Notion 文档,其中每个可申报 SRED 的项目都有一个子文档。
开始之前,请确保可以访问 Github、Notion 和 Linear。Notion 和 Linear 应使用 MCP 连接。Github 也可以通过 MCP 连接,但如果您有权访问 gh CLI 工具,也可以使用它。
如果其中任何一个无法访问,请提示用户在继续之前授予访问权限。
提示用户提供一个 Notion 文档链接,该文档是由 sred-work-summary 技能生成的上一年的工作总结。
确保:
该 notion 链接指向一个有效的文档,其格式大致如下:
总结: [X] 个 PR,[X] 个 Notion 文档,[X] 个 Linear 工单
*[仓库名称] [所有 PR 的链接]
[所有 Notion 文档的链接]
对于工作总结中的每个项目,根据 ${CLAUDE_SKILL_ROOT}/references/SRED.md 中对 SRED 项目的描述对其进行评估。这意味着查看项目的相关 Notion 文档和 PR,并确定项目工作是否看起来像是一个有效的 SRED 项目。对此要有规范性:能够归类为 SRED 项目的项目越多越好。
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
输出看起来符合 SRED 模型描述的项目列表,以及不符合该模型的项目列表。符合 SRED 描述的项目列表称为“可申报 SRED”项目。
确保:
询问用户可申报 SRED 项目列表是否正确。为他们提供手动将任何项目分类为可申报或不可申报的选项,并相应地调整列表。
创建一个名为“SRED 项目描述”的私有 Notion 文档。输出此文档的完整链接。
对于每个可申报 SRED 项目,执行一系列步骤。
步骤 1 创建一个名为“SRED 项目摘要 - ”的私有 Notion 文档,该文档是步骤 4 中创建的“SRED 项目描述”文档的子文档。该文档应遵循 ${CLAUDE_SKILL_ROOT}/references/project-template.md 中找到的模板。
步骤 2 填写该文档的 项目描述 和 项目目标 部分。使用文档这些部分中的 aside 部分作为提示,了解每个部分应包含哪些信息。使用工作总结中为每个项目收集的所有信息。使用项目的 Notion 文档以及您自己的推理来填写这些部分。
确保:
步骤 3 向用户提供该项目的“SRED 项目摘要”文档的完整 Notion 链接,并要求他们在继续之前进行审查。根据他们的要求进行任何更改。
步骤 4 每个项目将有一个或多个“不确定性”。“不确定性”由以下问题定义:
审查项目的所有 Notion 文档、Github PR 和 Linear 工单。确定项目存在哪些“不确定性”并向用户展示。询问用户这些是否正确或是否应以某种方式调整。
确保:
步骤 5 将“不确定性”添加到项目摘要 notion 文档的“技术不确定性”部分。
确保:
步骤 6 对于上面找到的每个“不确定性”,使用 Notion 文档、Github PR 和 Linear 工单来查找为应对此不确定性而进行的任何实验或尝试。在该“不确定性”的 实验 部分为每个已完成的实验制作一个要点列表。在 结果 / 经验教训 / 成功 部分制作一个要点列表,列出实验的结果以及得出的任何经验教训或结论。对于引用的任何 Notion 文档、Github PR 或 Linear 工单,请将该资源的链接放入“不确定性”的 特定于不确定性的文档和链接 部分。
确保:
步骤 7 获取工作总结中找到的项目的所有链接,对于任何未作为“不确定性”一部分链接的链接,将其包含在项目摘要的 项目文档和链接 部分。
确保:
步骤 8 再次向用户提供项目摘要文档的链接,并要求用户在继续处理下一个可申报 SRED 项目之前进行审查。提醒用户填写文档的“参与者”部分。
提供“SRED 项目描述” notion 文档的链接。
关于什么构成项目以及应如何组织的摘要:${CLAUDE_SKILL_ROOT}/references/SRED.md
特定项目摘要的 Notion 模板:${CLAUDE_SKILL_ROOT}/references/project-template.md
每周安装次数
186
仓库
GitHub Stars
454
首次出现
2026年2月19日
安全审计
安装于
codex169
claude-code167
opencode167
cursor166
gemini-cli166
kimi-cli164
SRED expects projects to be presented in a particular format. Take the list of projects that have been worked on in the past year, and summarize them into the format expected by SRED, with the supporting evidence. Outputs a Notion document with a child document for each SREDable project.
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.
Prompt the user for a link a Notion document, which is a Work Summary for the previous year produced by the sred-work-summary skill.
Ensure:
The notion links to a valid document that roughly matches this format:
Summary: [X] PRs, [X] Notion docs, [X] Linear tickets
*[repository name] [Links to all the PRs]
[Links to all the Notion docs]
For each project in the Work Summary, evaluate it against the description of a SRED project in ${CLAUDE_SKILL_ROOT}/references/SRED.md. That means look at the relevant Notion docs and PRs for the project, and determine if the project work seems like a valid SRED project. Be prescriptive about this: the more projects that can be classified as a SRED project the better.
Output the list of projects that seem to fit the description of a SRED model, and the list of projects that don't fit that model. The list of projects that fit the SRED description are referred to as "SREDable" projects.
Ensure:
Ask the user whether the list of SREDable projects is correct. Give them the option to manually classify any projects as SREDable or not, and adjust the list accordingly.
Create a private Notion document called "SRED Project Descriptions". Output the full link to this document.
For each SREDable project, go through a series of steps.
Step 1 Create a private Notion doc named "SRED Project Summary - " that is a child of the "SRED Project Description" document created in Step 4. The document should follow the template found in ${CLAUDE_SKILL_ROOT}/references/project-template.md.
Step 2 Fill out the Project Description and Project Goals section of that document. Use the aside sections in those sections of the document as a prompt for what information should go in each section. Use all the information for each project gathered in the Work Summary. Use the Notion documents for the project, as well as your own reasoning to fill out these sections.
Ensure:
Step 3 Provide the user the full Notion link to the "SRED Project Summary" document for the project and ask them to review it before continuing. Make any changes they ask for.
Step 4 Each project will have one or more Uncertainties. An Uncertainty is defined by the questions:
Review all the Notion documents, Github PRs and Linear tickets for the project. Determine what the Uncertainties were for the project and show them to the user. Ask the user whether these are correct or should be adjusted in some way.
Ensure:
Step 5 Add the Uncertainties to the Project Summary notion document in the "Technical Uncertainties" section.
Ensure:
Step 6 For each Uncertainty found above, use the Notion docs, Github PRs and Linear tickets to find any experiments or attempts that were done to address this uncertainty. Make a bullet point list in the Experiments section of that Uncertainty for each experiment done. Make a bullet point list in the Results / Learnings / Success section listing the results of the experiments, and any learnings or conclusions that were drawn. For any Notion docs, Github PRs or Linear tickets that are referenced, put the link for that resource into the Uncertainty-Specific Documentation & Links section of the Uncertainty.
Ensure:
Step 7 Take all of the links for the project found in the Work Summary, and for any that were not linked as part of an Uncertainty, include them in the Project Documentation & Links section of the Project Summary.
Ensure:
Step 8 Provide the user with the link to the Project Summary document again, and ask the user to review it before moving on to the next SREDable Project. Remind the user to fill out the Participants section of the document.
Provide a link to the "SRED Project Descriptions" notion document.
Example work summary: https://www.notion.so/sentry/SRED-Work-Summary-2026-30a8b10e4b5d81f5bc8df3553da55220
Summary of what constitutes a project and how it should be organized: ${CLAUDE_SKILL_ROOT}/references/SRED.md Notion Template of the summary for a specific project: ${CLAUDE_SKILL_ROOT}/references/project-template.md
Full documentation on the SRED program: https://www.canada.ca/en/revenue-agency/services/scientific-research-experimental-development-tax-incentive-program.html
Weekly Installs
186
Repository
GitHub Stars
454
First Seen
Feb 19, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykWarn
Installed on
codex169
claude-code167
opencode167
cursor166
gemini-cli166
kimi-cli164
GitHub Actions 官方文档查询助手 - 精准解答 CI/CD 工作流问题
45,200 周安装
AI创意写作助手 - 生成小说、诗歌、剧本、微小说,支持多种体裁风格
71 周安装
市场调研技能:全面指南与框架,助您分析竞争对手、识别市场机会
71 周安装
Python数据分析技能 - 掌握Pandas、NumPy数据操作与Jupyter工作流
71 周安装
Docker专家技能:NestJS/Next.js容器化、Docker Compose配置与微服务编排最佳实践
71 周安装
yfinance MCP 服务器 - 获取 Yahoo Finance 实时和历史金融数据 | 股票价格、期权、财报、新闻
71 周安装
Salesforce B2C Business Manager 扩展开发指南:自定义管理界面菜单、表单与对话框
71 周安装