// Format meeting content into structured meeting notes and archive them to your personal Yuque knowledge base. For personal/individual use — saves to your own repos.
| name | personal-meeting-notes |
| description | Format meeting content into structured meeting notes and archive them to your personal Yuque knowledge base. For personal/individual use — saves to your own repos. |
| license | Apache-2.0 |
| compatibility | Requires yuque-mcp server connected to a Yuque account with personal Token |
| metadata | {"author":"chen201724","version":"2.0"} |
Take raw meeting information from the user, format it into a standard meeting notes template, and create a document in the user's personal Yuque knowledge base.
All tools are from the yuque-mcp server:
yuque_list_repos — List personal knowledge bases to find the target repoyuque_create_doc — Create the meeting notes documentExtract or ask for the following from the user's input:
| Field | Required | Example |
|---|---|---|
| 会议主题 (Topic) | Yes | "Q1 产品规划评审" |
| 会议日期 (Date) | Yes (default: today) | "2024-01-15" |
| 会议时间 (Time) | No | "14:00-15:30" |
| 参会人员 (Attendees) | Yes | "张三、李四、王五" |
| 主持人 (Host) | No | "张三" |
| 记录人 (Recorder) | No | "AI 助手" |
If the user provides raw/unstructured content, extract these fields from context. If critical fields are missing (topic, attendees), ask the user.
Organize the meeting content into these sections:
For each action item, ensure it has:
Use this template:
# 会议纪要：[会议主题]
| 项目 | 内容 |
|------|------|
| 📅 日期 | YYYY-MM-DD |
| ⏰ 时间 | HH:MM - HH:MM |
| 📍 地点 | [线上/会议室名称] |
| 👥 参会人 | [姓名列表] |
| 🎙️ 主持人 | [姓名] |
| ✍️ 记录人 | [姓名/AI 助手] |
---
## 📋 议题
1. [议题 1]
2. [议题 2]
3. [议题 3]
---
## 💬 讨论要点
### 议题 1：[标题]
- [要点 1]
- [要点 2]
- [要点 3]
### 议题 2：[标题]
- [要点 1]
- [要点 2]
---
## ✅ 决议
1. **[决议 1]**
- 说明：[补充细节]
2. **[决议 2]**
- 说明：[补充细节]
---
## 📌 待办事项
| # | 事项 | 负责人 | 截止日期 | 状态 |
|---|------|--------|----------|------|
| 1 | [具体任务] | [姓名] | YYYY-MM-DD | ⬜ 待开始 |
| 2 | [具体任务] | [姓名] | YYYY-MM-DD | ⬜ 待开始 |
| 3 | [具体任务] | [姓名] | YYYY-MM-DD | ⬜ 待开始 |
---
## 📝 备注
- [其他需要记录的内容]
---
> 本纪要由 AI 助手整理，如有遗漏请补充。
List the user's personal knowledge bases:
Tool: yuque_list_repos
Parameters:
type: "user"
If the user hasn't specified a repo:
Tool: yuque_create_doc
Parameters:
repo_id: "<namespace>" # e.g., "username/meeting-notes"
title: "会议纪要：[主题] - YYYY-MM-DD"
body: "<formatted markdown content>"
format: "markdown"
After creation, respond with:
✅ 会议纪要已创建！
📄 **[会议纪要：主题 - 日期](文档链接)**
📚 已归档到：「个人知识库名称」
### 摘要
- 共讨论 X 个议题
- 形成 X 项决议
- 产生 X 个待办事项
team-meeting-notes| Situation | Action |
|---|---|
| User provides very little info | Ask for at least: topic, attendees, key decisions |
yuque_list_repos returns empty | Ask user for the exact repo name or ID |
yuque_create_doc fails (403) | Tell user they may lack write permission to this repo |
yuque_create_doc fails (other) | Show error, suggest user check yuque-mcp connection |
| No clear action items | Still create the doc, note "本次会议无明确待办事项" |
| User wants to save to team repo | Suggest using team-meeting-notes skill instead |
Search your personal Yuque knowledge bases with natural language queries and provide summarized answers with key points and source links. For personal/individual use — searches across your own documents.
Generate comprehensive monthly knowledge management reports by analyzing team Yuque activity data including group stats, member contributions, knowledge base health, and document trends. For team use — requires team Token with statistic:read permission.
Format meeting content into structured meeting notes and archive them to a group Yuque knowledge base. For group use — saves to team/group repos. Requires group Token.
Automatically compile a team's core Yuque documents into a structured onboarding reading guide for new group members. For group use — scans group knowledge bases and generates a prioritized reading plan. Requires group Token.
Search group Yuque knowledge bases with natural language queries and provide summarized answers with key points and source links. For group use — searches within team/group repositories. Requires group Token.
Generate technical design documents using a standard template and save them to a group Yuque knowledge base. For group use — stores designs in group repos with review workflow. Requires group Token.