免费在 GitHub 公开中文介绍

prep-with-circleback

从 Circleback 日程、过往会议、未完成任务和邮件中整理会前简报，列出参会者及其角色、近期决定、双方待办和未解决问题，并附上来源链接。

原文查看原文说明

Build a brief for an upcoming meeting from Circleback — the calendar event, the history with the same people and company, open commitments on both sides, and what is still unresolved. Use when the user asks to prep for a call, "what do I need to know before", who someone is, or where things stand with a customer or partner.

ParadevAI/Paradev星标 15,720(GitHub 15,720 + cccskills 0)

实测评分未实测

查看安装方法

适用场景

准备客户会议
确认参会者及其角色
整理双方未完成的承诺
会前核对未解决事项

中文介绍

功能

此技能从 Circleback 的日程、过往会议、未完成任务和邮件中整理简短的会前备忘。内容包括参会者及其角色、最近的决定及日期、我方和对方尚未完成的事项，以及仍待解决的问题。每项内容都会附上对应会议、日程或邮件线程的链接，便于查看依据。

适用场景

与客户或合作伙伴开会前，如果需要了解当前进展并确认该讨论什么，可以使用此技能。它会查看与相同人员或公司最近的两三次会议；如果双方交往已久，也会参考最早的一次会议。简报以待解决事项为重点，控制在大约一个屏幕内，不逐一复述所有历史会议。

使用示例

“请整理今天与客户开会前需要了解的要点。”
“请把我方和对方尚未完成的事项分开列出。”
“请列出下次合作伙伴会议需要确认的问题。”

注意事项

此技能需要使用 Circleback 日程、会议、任务和邮件搜索工具。未指定时间范围时，日程搜索默认查找今天和明天。参会者角色依据个人资料或记录；无法确认时会标明未知。生成的见解不会当作已确认事实。定期会议应先确认具体日期，再查阅历史记录。

本介绍由 AI（OpenAI Codex）根据公开的 SKILL.md 撰写。准确的规格请查看下方原文。

文档检查

AI 根据 SKILL.md 的内容检查了需要注意的操作和使用前提。评分只依据实际运行的结果（实测对比）。

安全性发送数据、删除文件、执行命令等是否有说明: A良好资料限定为搜索 Circleback 记录，并规定未知角色和生成见解的标注方式。
安装难易度所需工具和 API 密钥是否少且有说明: B部分不足需要 Circleback 搜索工具，但未说明连接或安装步骤。

不计入评分。由 AI（OpenAI Codex）于 2026年10月29日评估。仅供参考，安装前请同时查看原文。

如果您认为评估有误，请申请复核

包含的文件（1）

SKILL.md2.9 KB

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

Brief before the meeting

A good brief is short, and every line in it comes from a source the user can open. The job is to reconstruct where things stand with these people from what Circleback captured, and to lead with what is unresolved.

1. Anchor on the event

SearchCalendarEvents for the window the user means (default: today and tomorrow). Take the attendees and organizer from the event — that is the guest list, not your guess. If the user named a person or company instead, resolve them with FindProfiles or FindCompanies and skip the calendar.

2. Pull the history with these people

SearchMeetings filtered by the attendees' profiles or the company domain, newest first. Read the last two or three with ReadMeetings. For a long relationship read the most recent and the first: the first records what they wanted, the most recent records what they got.

3. Find the open loops on both sides

The meetings you just read already carry their action items, each with a status and an assignee. Take the open ones from there first, yours and theirs. Reach for SearchActionItems (status PENDING, by assignee profile) only for what those meetings cannot show: a standalone item, or one from a call you did not read. An open item from the last call is the first thing the other side will ask about. SearchEmails fills the gap between meetings when a thread continued in writing.

4. Write the brief in that order

Who is coming and their role, one line each.
Where things stand: the last decision and the date it was made.
Open on our side, open on theirs, with the meeting each came from.
Unresolved questions the user should be ready for.

Keep it to a screen. Every line links to the meeting, event, or email thread it came from.

Anti-patterns

Summarizing every past meeting. The brief is about what is open, not a history lesson.
Guessing roles from titles. Take names and roles from the profile and the notes; say "unknown" otherwise.
Presenting insights as facts. Generated insights get a "Circleback suggests" label or get left out.
Prepping for the wrong meeting. A recurring series has one event per week; confirm the date before pulling history.

评价

还没有评价。欢迎分享你的使用感受。

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

同一仓库的技能