process-meeting-transcript

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Process Meeting Transcript

处理会议转录文本

Overview

概述

Process raw meeting transcripts into well-structured Obsidian notes with YAML frontmatter, extracted action items, meeting summary, and properly formatted transcript sections.

将原始会议转录文本处理为结构清晰的Obsidian笔记，包含YAML frontmatter、提取出的待办事项、会议摘要以及格式规范的转录文本段落。

When to Use This Skill

何时使用该技能

Use this skill when:

User provides a raw meeting transcript (typically from Granola)
User asks to "process a meeting transcript" or "format meeting notes"
User points to a file containing an unprocessed transcript
User pastes transcript content directly into the conversation

符合以下场景时可使用该技能：

用户提供原始会议转录文本（通常来自Granola）
用户要求“处理会议转录文本”或“格式化会议笔记”
用户指向包含未处理转录文本的文件
用户直接在对话中粘贴转录文本内容

Workflow

工作流

Step 1: Read the Transcript

步骤1：读取转录文本

If the transcript is in a file, read the entire contents. If the user pasted the transcript directly, use that content.

如果转录文本存储在文件中，请读取全部内容。如果用户直接粘贴了转录文本，直接使用该内容即可。

Step 2: Extract Action Items

步骤2：提取待办事项

Carefully review the entire transcript to identify all action items, tasks, and commitments. Look for:

Explicit commitments: "I'll do X", "Alex will review Y"
Assigned tasks: "Nathan and Damian should schedule..."
Follow-up items: "We need to...", "Let's make sure to..."
Decisions requiring action: "We should deploy X before Y"

Format action items as:

Bulleted list under
```
# Action Items
```
heading
Use bold for person names when specific people are assigned
Include context for what needs to be done and why
Order by priority/importance when evident from discussion

Example format:

markdown

undefined

仔细审阅全部转录文本，识别所有待办事项、任务和承诺。重点留意以下内容：

明确承诺：例如"I'll do X"、"Alex will review Y"
分配的任务：例如"Nathan and Damian should schedule..."
后续跟进项：例如"We need to..."、"Let's make sure to..."
需要落地的决策：例如"We should deploy X before Y"

待办事项格式要求：

在
```
# Action Items
```
标题下使用无序列表展示
若指定了具体负责人，姓名使用加粗格式
包含待办事项的具体内容和背景原因
若讨论中明确了优先级，按优先级/重要性排序

示例格式：

markdown

undefined

Action Items

Alice & Bob: Review the new feature implementation next week and provide feedback
Charlie & Dana: Schedule a knowledge transfer session on the payment service architecture
Eve: Discuss deployment timeline with the infrastructure team

undefined

Alice & Bob: Review the new feature implementation next week and provide feedback
Charlie & Dana: Schedule a knowledge transfer session on the payment service architecture
Eve: Discuss deployment timeline with the infrastructure team

undefined

Step 3: Create Meeting Summary

步骤3：生成会议摘要

Write a comprehensive but concise summary that captures:

Main topics discussed
Key decisions made
Technical architecture or approach agreed upon
Timeline and next steps
Important context or constraints

Structure the summary with:

Opening paragraph: High-level overview of what was discussed and main outcome
Subsections (using
```
##
```
or
```
###
```
headings) for major topics
Use bold for important terms, decisions, or concepts
Include enough detail that someone who wasn't in the meeting can understand what happened

Keep summaries factual and focused on outcomes, decisions, and technical details.

撰写全面且简洁的摘要，需覆盖以下内容：

讨论的主要议题
做出的关键决策
达成一致的技术架构或落地方案
时间线及后续步骤
重要背景或限制条件

摘要结构要求：

开篇段落：概述会议讨论内容及核心成果
针对主要议题使用
```
##
```
或
```
###
```
标题划分小节
重要术语、决策或概念使用加粗格式突出
包含足够细节，确保未参会人员也能清晰理解会议内容

摘要需保持客观，聚焦成果、决策和技术细节。

Step 4: Format the Transcript

步骤4：格式化转录文本

Place the raw transcript under a

# Transcript

heading. Preserve the original formatting but ensure it's readable. If the transcript includes metadata (meeting title, date, participants) at the top, keep that information.

将原始转录文本放在

# Transcript

标题下。保留原始格式的同时确保内容可读。如果转录文本顶部包含元数据（会议标题、日期、参会人员），请保留该部分信息。

Step 5: Add Frontmatter

步骤5：添加Frontmatter

Use the

add-frontmatter

slash command to generate appropriate YAML frontmatter for the note. The frontmatter should include:

```
title
```
: Meeting title or topic
```
date
```
: Meeting date (YYYY-MM-DD format)
```
type
```
: Set to "meeting"
```
attendees
```
: Array of participant names
```
project
```
: Related project if applicable
```
tags
```
: Relevant tags (meeting, project tags, topic tags)
```
status
```
: Set to "complete"
```
key_topics
```
: Array of main discussion topics
```
action_items
```
: Array of action items (duplicate from Action Items section for searchability)
```
decisions
```
: Array of key decisions made
```
related_links
```
: Any links mentioned (Notion docs, Linear issues, etc.)

Invoke the add-frontmatter command by providing it with context about the meeting.

使用

add-frontmatter

斜杠命令为笔记生成合适的YAML frontmatter。frontmatter需包含以下字段：

```
title
```
: 会议标题或议题
```
date
```
: 会议日期（YYYY-MM-DD格式）
```
type
```
: 固定设置为"meeting"
```
attendees
```
: 参会人员姓名数组
```
project
```
: 关联项目（如适用）
```
tags
```
: 相关标签（会议标签、项目标签、议题标签等）
```
status
```
: 固定设置为"complete"
```
key_topics
```
: 主要讨论议题数组
```
action_items
```
: 待办事项数组（为便于搜索，与Action Items部分内容重复）
```
decisions
```
: 关键决策数组
```
related_links
```
: 会议中提及的所有链接（Notion文档、Linear issue等）

通过提供会议相关上下文来调用add-frontmatter命令。

Step 6: Assemble the Final Note

步骤6：组装最终笔记

Combine all sections in this order:

YAML frontmatter (from add-frontmatter command)
Links section (if any Notion/Linear/GitHub links were mentioned)
```
# Action Items
```
section
```
# Summary
```
section
```
# Transcript
```
section

按以下顺序组合所有内容板块：

YAML frontmatter（来自add-frontmatter命令生成结果）
链接板块（如果会议中提及了Notion/Linear/GitHub相关链接）
```
# Action Items
```
板块
```
# Summary
```
板块
```
# Transcript
```
板块

Output Format

输出格式

The final note should follow this structure:

markdown

---
title: Meeting Title
date: YYYY-MM-DD
type: meeting
attendees: ['Person 1', 'Person 2', ...]
project: Project Name
tags: [meeting, relevant, tags]
status: complete
key_topics:
  - Topic 1
  - Topic 2
action_items:
  - 'Action item 1'
  - 'Action item 2'
decisions:
  - Decision 1
  - Decision 2
related_links:
  - 'Link description: URL'
---

**Agenda** https://link-to-agenda-if-available

最终笔记需遵循以下结构：

markdown

---
title: Meeting Title
date: YYYY-MM-DD
type: meeting
attendees: ['Person 1', 'Person 2', ...]
project: Project Name
tags: [meeting, relevant, tags]
status: complete
key_topics:
  - Topic 1
  - Topic 2
action_items:
  - 'Action item 1'
  - 'Action item 2'
decisions:
  - Decision 1
  - Decision 2
related_links:
  - 'Link description: URL'
---

**Agenda** https://link-to-agenda-if-available

Action Items

Person: Action item description
Person: Another action item

Person: Action item description
Person: Another action item

Summary

Opening paragraph with high-level overview.

Key Decisions/Topics

Details about decisions and topics discussed...

Transcript

[Raw transcript content]

undefined

[Raw transcript content]

undefined

Tips for Quality Output

高质量输出提示

Be thorough with action items: Don't miss commitments buried in discussion
Capture decisions: Explicit decisions are critical for reference
Include technical details: Preserve architecture discussions, API names, service names
Maintain context: Someone reading later should understand what was decided and why
Preserve links: Notion docs, Linear issues, GitHub PRs mentioned in meetings are important
Use consistent formatting: Follow the example structure for all transcripts

全面提取待办事项：不要遗漏隐藏在讨论中的承诺内容
完整记录决策：明确的决策对后续参考至关重要
保留技术细节：完整留存架构讨论、API名称、服务名称等技术信息
保留上下文信息：确保后续阅读笔记的人能够理解决策内容和决策原因
留存所有链接：会议中提到的Notion文档、Linear issue、GitHub PR都是重要参考信息
使用统一格式：所有转录文本的处理都遵循上述示例结构