Meeting Notes
outline/outline
Create meeting notes in Outline from a template; use when the user wants an agenda, notes, or a follow-up document for a meeting.
将会议录音文字稿、笔记或聊天记录等原始材料整理为结构化会议纪要，自动提取议题、讨论要点、结论以及包含负责人与截止日期的行动项。当用户提供会议素材并提及会议记录、纪要、meeting minutes、会议总结、行动项、整理会议或会后跟踪等关键词时触发。
Install Meeting Recap
$ npx skills add rongxinzy/RongxinAI --skill meeting-recap -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rongxinzy/RongxinAI meeting-recap --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/rongxinzy/RongxinAI.git skills-src && mkdir -p .claude/skills && cp -r skills-src/SKILLs/meeting-recap .claude/skills/meeting-recap && 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 "meeting-recap" agent skill from https://github.com/rongxinzy/RongxinAI/tree/main/SKILLs/meeting-recap into .claude/skills/meeting-recap/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-recap", 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/rongxinzy/RongxinAI/tree/main/SKILLs/meeting-recapType 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 rongxinzy/RongxinAI --skill meeting-recap -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rongxinzy/RongxinAI meeting-recap --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rongxinzy/RongxinAI.git skills-src && mkdir -p .agents/skills && cp -r skills-src/SKILLs/meeting-recap .agents/skills/meeting-recap && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "meeting-recap" agent skill from https://github.com/rongxinzy/RongxinAI/tree/main/SKILLs/meeting-recap into .agents/skills/meeting-recap/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-recap", 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 rongxinzy/RongxinAI --skill meeting-recap -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rongxinzy/RongxinAI meeting-recap --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rongxinzy/RongxinAI.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/SKILLs/meeting-recap .cursor/skills/meeting-recap && 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 "meeting-recap" agent skill from https://github.com/rongxinzy/RongxinAI/tree/main/SKILLs/meeting-recap into .cursor/skills/meeting-recap/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-recap", 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/rongxinzy/RongxinAI.git --path SKILLs/meeting-recap--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 rongxinzy/RongxinAI --skill meeting-recap -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rongxinzy/RongxinAI meeting-recap --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rongxinzy/RongxinAI.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/SKILLs/meeting-recap .gemini/skills/meeting-recap && 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 "meeting-recap" agent skill from https://github.com/rongxinzy/RongxinAI/tree/main/SKILLs/meeting-recap into .gemini/skills/meeting-recap/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-recap", 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 rongxinzy/RongxinAI meeting-recapInstalls 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 rongxinzy/RongxinAI --skill meeting-recap -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rongxinzy/RongxinAI.git skills-src && mkdir -p .github/skills && cp -r skills-src/SKILLs/meeting-recap .github/skills/meeting-recap && 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 "meeting-recap" agent skill from https://github.com/rongxinzy/RongxinAI/tree/main/SKILLs/meeting-recap into .github/skills/meeting-recap/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-recap", 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 rongxinzy/RongxinAI --skill meeting-recap -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rongxinzy/RongxinAI meeting-recap --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rongxinzy/RongxinAI.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/SKILLs/meeting-recap .opencode/skills/meeting-recap && 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 "meeting-recap" agent skill from https://github.com/rongxinzy/RongxinAI/tree/main/SKILLs/meeting-recap into .opencode/skills/meeting-recap/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "meeting-recap", 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
meeting-recap- GitHub stars
- 154
- Token cost
- ~1.1k tokens
- SKILL.md length
- 225 words
- Files
- 5 (incl. scripts)
- Skills in repo
- 94
- Repo updated
- First seen
- Licence
- MIT
At a glance
将会议录音文字稿、笔记或聊天记录等原始材料整理为结构化会议纪要，自动提取议题、讨论要点、结论以及包含负责人与截止日期的行动项。当用户提供会议素材并提及会议记录、纪要、meeting minutes、会议总结、行动项、整理会议或会后跟踪等关键词时触发。
- Works in 7 steps: ：输入收集与预处理 → ：议题识别与分段 → ：逐议题深度提取 → …
- Tasks that involve Meeting notes and agendas
- SKILL.md covers Quick Start, SOP 流程, 参数说明 and 常见场景示例
- Runs Python scripts from its folder; calls python3
What it does
Meeting Recap is an agent skill from rongxinzy/RongxinAI. 将会议录音文字稿、笔记或聊天记录等原始材料整理为结构化会议纪要，自动提取议题、讨论要点、结论以及包含负责人与截止日期的行动项。当用户提供会议素材并提及会议记录、纪要、meeting minutes、会议总结、行动项、整理会议或会后跟踪等关键词时触发。
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts (for example `scripts/validate_minutes.py` and `zhiyuan/metadata.yaml`).
It sits in Productivity & Automation, covering Meeting notes and agendas. The repository describes itself as: An all-in-one local AI Agent workspace with a fully self-developed stack. The licence is MIT.
When your agent uses it
- Tasks that involve Meeting notes and agendas
Example prompts
- “/meeting-recap”
Requirements
- Python 3
Workflow steps
7 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 9c64865. 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
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Meeting Recap loads about 1.1k tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 225 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); the scripts in this folder are not scanned.
SKILL.md
The full file from rongxinzy/RongxinAI at commit 9c64865, republished under its MIT licence (© rongxinzy). 225 words, ~1,130 tokens.
Download SKILL.mdSave it as
.claude/skills/meeting-recap/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- meeting-recap
- description
- 将会议录音文字稿、笔记或聊天记录等原始材料整理为结构化会议纪要，自动提取议题、讨论要点、结论以及包含负责人与截止日期的行动项。当用户提供会议素材并提及会议记录、纪要、meeting minutes、会议总结、行动项、整理会议或会后跟踪等关键词时触发。
- license
- MIT
Meeting Minutes — 会议记录→结构化纪要 SOP
将零散的会议原始记录（文字稿、笔记、聊天记录）转化为专业的结构化会议纪要，自动提取议题、结论和行动项。
Quick Start
- 用户提供会议原始材料（文字稿 / 笔记 / 粘贴文本）
- Agent 按下方 SOP 逐步处理
- 输出结构化纪要，可选运行
scripts/validate_minutes.py校验完整性 - 用户确认后，可导出为 Markdown 文件
SOP 流程
Phase 1：输入收集与预处理
目标：确认原始素材类型，补全缺失的元信息。
步骤：
识别素材类型，向用户确认：
- 语音转文字稿（ASR transcript）
- 手工笔记
- IM 聊天记录（飞书/Slack/微信群）
- 混合素材
提取或询问元信息（以下字段均为必填）：
字段 说明 示例 会议名称 本次会议的主题名 Q2 产品评审会 日期 YYYY-MM-DD 格式 2026-04-14 时间 HH:MM-HH:MM 14:00-15:30 地点/方式 线下会议室或线上工具 飞书会议 主持人 会议组织者 张三 记录人 填写纪要的人 AI 辅助 参会人 所有参与者列表 张三、李四、王五 如果素材中缺少上述任何字段，主动询问用户补充。不要猜测参会人或日期。
Phase 2：议题识别与分段
目标：将连续的会议内容拆分为独立议题。
方法：
通读全文，识别话题切换点。常见信号：
- 明确的议题引入语（"下一个话题"、"接下来讨论"、"关于 XX"）
- 发言人变化 + 主题变化
- 时间戳跳跃（如有）
为每个议题编号并命名，格式：
议题 1：[简洁标题，≤15字] 议题 2：[简洁标题，≤15字] ...特殊处理规则：
- 如果一个话题中途被打断、后续又回来了，合并为同一议题
- 简短的寒暄/闲聊不单独成题，忽略或归入"其他"
- 如果整个会议只有一个主题，也要明确标注为"议题 1"
将议题列表展示给用户确认，再进入下一步。
Phase 3：逐议题深度提取
目标：对每个议题提取结构化信息。
对每个议题，按以下模板提取：
### 议题 N：[标题]
**背景**：（1-2 句话，为什么要讨论这件事）
**讨论要点**：
- [要点1]：[核心观点/数据/方案]（发言人：XX）
- [要点2]：[核心观点/数据/方案]（发言人：XX）
- ...
**分歧与争议**：（如有）
- [争议点]：A 方认为…… / B 方认为……
**结论/决策**：
- ✅ [明确的结论，使用陈述句]
- ✅ [如有多条结论逐条列出]
**行动项**：
| 序号 | 任务描述 | 负责人 | 截止日期 | 优先级 |
|------|----------|--------|----------|--------|
| 1 | [具体可执行的任务] | [姓名] | YYYY-MM-DD | 高/中/低 |提取规则：
- 讨论要点：保留关键信息，删除重复/口语化内容。每条 ≤ 50 字。
- 结论：必须是已达成共识的决策，不是"继续讨论"。如果没有明确结论，标注"待定：需 [条件] 后再议"。
- 行动项提取标准（必须同时满足以下条件才提取为行动项）：
- 有明确的"做什么"（动词 + 宾语）
- 有明确或可推断的负责人
- 是具体可执行的任务，而非方向性描述
- 截止日期处理：
- 原文明确提到日期 → 直接使用
- 原文说"下周"/"月底"等模糊表述 → 转换为具体日期并标注
（推算） - 完全没提到 → 标注"待确认"并在备注中提醒用户
- 优先级判断：
- 高：阻塞其他工作 / 有明确紧迫 deadline / 被多次强调
- 中：有 deadline 但不紧急 / 常规跟进
- 低：Nice-to-have / 探索性任务
Phase 4：全局信息提取
目标：提取跨议题的全局信息。
遗留问题（未达成结论、需要后续讨论的事项）：
markdown ## 遗留问题 | 序号 | 问题描述 | 相关议题 | 后续计划 | |------|----------|----------|----------| | 1 | [问题] | 议题 N | [下次会议讨论 / 需XX补充材料] |风险提示（Agent 在整理过程中发现的潜在风险）：
markdown ## ⚠️ 风险提示 - [风险1]：[描述]（来源：议题 N） - [风险2]：[描述]常见风险信号：deadline 冲突、资源不足、依赖不明确、多个行动项无人认领。
关键数据/指标（如会议中提到了具体数字）：
markdown ## 关键数据 - [指标名称]：[数值]（来源：议题 N）
Phase 5：组装输出
目标：将所有提取结果组装为完整纪要。
输出模板：
# 会议纪要：[会议名称]
| 项目 | 内容 |
|------|------|
| 日期 | YYYY-MM-DD |
| 时间 | HH:MM - HH:MM |
| 地点 | [地点/线上工具] |
| 主持人 | [姓名] |
| 记录人 | [姓名] |
| 参会人 | [姓名列表] |
---
## 议题概览
| 议题 | 结论状态 | 行动项数 |
|------|----------|----------|
| 议题 1：[标题] | ✅ 已决策 / ⏳ 待定 | N |
| 议题 2：[标题] | ✅ 已决策 / ⏳ 待定 | N |
---
## 详细记录
### 议题 1：[标题]
（Phase 3 提取的完整内容）
### 议题 2：[标题]
（Phase 3 提取的完整内容）
---
## 行动项汇总
| 序号 | 任务描述 | 负责人 | 截止日期 | 优先级 | 来源议题 |
|------|----------|--------|----------|--------|----------|
| 1 | [任务] | [姓名] | YYYY-MM-DD | 高/中/低 | 议题 N |
| ... | | | | | |
## 遗留问题
（Phase 4 内容）
## ⚠️ 风险提示
（Phase 4 内容，如无则省略此节）
## 关键数据
（Phase 4 内容，如无则省略此节）Phase 6：质量校验
目标：确保纪要完整、准确、可执行。
自动校验清单（逐项检查并报告）：
- 所有元信息字段已填写（无"未知"或空值）
- 每个议题都有结论（即使是"待定"）
- 每个行动项都有负责人（无"待确认"的负责人）
- 每个行动项都有截止日期（可以是"待确认"但需标注）
- 行动项汇总表的条数 = 各议题行动项之和
- 没有出现原文中未提及的人名（防止幻觉）
- 日期格式统一为 YYYY-MM-DD
- 纪要中引用的数据与原文一致
可运行验证脚本：完成纪要后，可使用 scripts/validate_minutes.py 对输出的 Markdown 文件做结构化校验。
python3 scripts/validate_minutes.py <纪要文件.md>脚本会检查：
- 必填章节是否存在
- 行动项表格格式是否完整
- 截止日期格式是否规范
- 负责人是否为空
- 议题概览与详细记录的数量是否一致
Phase 7：交付与后续
展示纪要给用户确认，重点关注：
- "行动项是否准确？有没有遗漏？"
- "结论是否反映了实际讨论结果？"
- "有没有需要补充或修改的内容？"
根据用户反馈修订，直到用户确认。
导出选项：
- 保存为 Markdown 文件
- 如用户需要其他格式（飞书文档、Word），告知可使用对应 skill 转换
参数说明
本 skill 不需要外部参数。以下为可选的定制项：
| 配置项 | 默认值 | 说明 |
|---|---|---|
| 语言 | 中文 | 纪要输出语言，跟随原始素材语言 |
| 行动项优先级 | 启用 | 是否标注优先级（高/中/低） |
| 风险提示 | 启用 | 是否生成风险提示章节 |
| 关键数据 | 启用 | 是否提取会议中提到的数字/指标 |
常见场景示例
场景 1：语音转文字稿整理
用户贴入飞书妙记或 Otter.ai 导出的文字稿，Agent 按 SOP 整理为结构化纪要。
场景 2：IM 聊天记录整理
用户贴入微信群/飞书群的讨论记录，Agent 识别议题并提取行动项。
场景 3：手写笔记整理
用户贴入自己在会议中随手记的要点，Agent 补充结构并确认遗漏。
场景 4：跨时区英文会议
用户提供英文 transcript，Agent 可按同样流程处理并输出中文或英文纪要。
© rongxinzy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (scripts) in SKILLs/meeting-recap of rongxinzy/RongxinAI.
- SKILL.md
- LICENSE
- scripts/validate_minutes.py
- zhiyuan/icon.png
- zhiyuan/metadata.yaml
Open the folder on GitHubat commit 9c64865
Compare with similar skills
Meeting Recap 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 |
|---|---|---|---|---|---|---|
| Meeting Recap this skillrongxinzy/RongxinAI | 154 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Meeting Notesoutline/outline | 41k | — | ~551 | Automated safety check: Pass | Custom licence | |
| Management Talkthananon/9arm-skills | 3.2k | — | ~3.2k | Automated safety check: Pass | None | |
| Challenge Baseline ModelAgibotTech/genie_sim | 1.4k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Handwriting Stand Uplimin112/min-skill | 454 | — | ~2.5k | Automated safety check: Pass | None | |
| Daily Journalravila4/claude-adhd-skills | 158 | — | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
Management Talk
thananon/9arm-skills
Rewrite engineer-to-engineer content for engineering-org leadership (VPs, directors, PMs, release managers, execs in an engineering-savvy company) and shape it for the channel it is going to — JIRA…
Challenge Baseline Model
AgibotTech/genie_sim
Provision and launch the Simulation Challenge baseline inference model end to end: clone the inference code from a given git repo/branch, download the checkpoints from ModelScope into the repo's…
Handwriting Stand Up
limin112/min-skill
Turn a screen recording of handwriting (or a photo of handwritten text) into a single-file HTML "continuation" — the recording plays, the ink lifts off the page as solid 3D letters, a short animated…
Daily Journal
ravila4/claude-adhd-skills
Draft, organize, or update development journal entries. An agent skill from ravila4/claude-adhd-skills.
Granola
ArtemXTech/claude-code-obsidian-starter
Query and sync Granola meetings to Obsidian vault. An agent skill from ArtemXTech/claude-code-obsidian-starter.
More from rongxinzy/RongxinAI
All 94 skills in this repoSaaS Metrics Coach
rongxinzy/RongxinAI
SaaS financial health advisor. An agent skill from rongxinzy/RongxinAI.
Churn Prevention
rongxinzy/RongxinAI
Reduce voluntary and involuntary churn through cancel flow design, save offers, exit surveys, and dunning sequences.
Presentation Studio
rongxinzy/RongxinAI
The only skill for creating a new PowerPoint deck. An agent skill from rongxinzy/RongxinAI.
Zhiyuan Expert Manager
rongxinzy/RongxinAI
ZhiYuan Agent expert package lifecycle manager for the pi engine.
Ziwei Doushu
rongxinzy/RongxinAI
Professional Ziwei Doushu consultation skill with an offline calculation engine.
Lark Mail
rongxinzy/RongxinAI
飞书邮箱：Use when user mentions 起草邮件、写邮件、草稿、发送/回复/转发邮件、查阅邮件、看邮件、搜索邮件、邮件文件夹、邮件标签、邮件联系人、监听新邮件、邮件收信规则等；use for mail/email intent only.
Related
Categories
Questions about Meeting Recap
What does Meeting Recap do?
将会议录音文字稿、笔记或聊天记录等原始材料整理为结构化会议纪要，自动提取议题、讨论要点、结论以及包含负责人与截止日期的行动项。当用户提供会议素材并提及会议记录、纪要、meeting minutes、会议总结、行动项、整理会议或会后跟踪等关键词时触发。. Meeting Recap is an agent skill from rongxinzy/RongxinAI.
When should I use Meeting Recap?
Meeting Recap fits situations like: tasks that involve Meeting notes and agendas.
How do I install Meeting Recap in Claude Code?
Run `npx skills add rongxinzy/RongxinAI --skill meeting-recap -a claude-code`. Or copy the skill folder (SKILLs/meeting-recap in rongxinzy/RongxinAI) into .claude/skills/meeting-recap in your project. Claude Code loads it when a task matches its description.
How do I install Meeting Recap in Codex?
Run `npx skills add rongxinzy/RongxinAI --skill meeting-recap -a codex`. Or copy the skill folder (SKILLs/meeting-recap in rongxinzy/RongxinAI) into .agents/skills/meeting-recap in your project. Codex loads it when a task matches its description.
Can I use Meeting Recap 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 rongxinzy/RongxinAI --skill meeting-recap -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/meeting-recap, .gemini/skills/meeting-recap, .github/skills/meeting-recap and .opencode/skills/meeting-recap in your project.
What does Meeting Recap need to run?
Going by SKILL.md and its folder, Meeting Recap needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Meeting Recap access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Meeting Recap 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Meeting Recap use?
Meeting Recap is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Meeting Recap use?
About 1.1k tokens (SKILL.md is roughly 4.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 Meeting Recap?
Skills that share tags, products or a category with Meeting Recap: Meeting Notes (outline/outline, 41k stars), Management Talk (thananon/9arm-skills, 3.2k stars), Challenge Baseline Model (AgibotTech/genie_sim, 1.4k stars) and Handwriting Stand Up (limin112/min-skill, 454 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Meeting Recap?
rongxinzy (a GitHub organization) maintains it in rongxinzy/RongxinAI, which has 154 GitHub stars. The repository holds 94 skills in this directory. The repository was last updated on October 10, 2026.
Source: rongxinzy/RongxinAI on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.