Take raw meeting information from the user, format it into a standard meeting notes template, and create a document in the team's Yuque knowledge base.
When to Use
- User shares meeting content and wants it saved to the team's Yuque
- User says "Help me organize the meeting minutes into the team library", "save meeting notes to group repo", "Save the meeting record to the team knowledge base"
- User pastes unstructured meeting notes and wants them formatted and saved to group repo
Required MCP Tools
All tools are from the yuque-mcp server:
yuque_list_repos— List group knowledge bases to find the target repoyuque_create_doc— Create the meeting notes document
Workflow
Step 1: Gather Meeting Information
Extract or ask for the following from the user's input:
| Field | Required | Example |
|---|---|---|
| Meeting Topic (Topic) | Yes | "Q1 Product Planning Review" |
| Meeting Date (Date) | Yes (default: today) | "2024-01-15" |
| Meeting Time (Time) | No | "14:00-15:30" |
| Attendees (Attendees) | Yes | "Zhang San, Li Si, Wang Wu" |
| Host (Host) | No | "Zhang San" |
| Recorder (Recorder) | No | "AI Assistant" |
| Group login (Group login) | Yes | "my-team" |
If the user provides raw/unstructured content, extract these fields from context. If critical fields are missing (topic, attendees), ask the user.
If the user hasn't specified a group login, ask: "Please tell me your team's Yuque group login, and I'll save the meeting minutes to the team knowledge base."
Step 2: Structure the Content
Organize the meeting content into these sections:
- Agenda Items (Agenda Items) — What was discussed
- Discussion Points (Discussion Points) — Key arguments, opinions, data shared
- Decisions (Decisions) — What was decided
- Action Items (Action Items) — Who does what by when
- Notes (Notes) — Anything else worth recording
For each action item, ensure it has:
- Owner (Owner): Who is responsible
- Due Date (Deadline): When it's due
- Specifics (Description): What needs to be done
Step 3: Format the Document
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 助手整理，如有遗漏请补充。
Step 4: Find Team Repository
List the team's knowledge bases:
Tool: yuque_list_repos
Parameters:
login: "<group_login>"
type: "group"
If the user hasn't specified a repo:
- List available group repos and ask the user to pick one
- If there's an obvious "Meeting Minutes" or "Meeting Notes" repo, suggest it
- If the user says "just put it in that meeting's repo", match by name
Step 5: Create the Document
Tool: yuque_create_doc
Parameters:
repo_id: "<namespace>" # e.g., "my-team/meeting-notes"
title: "会议纪要：[主题] - YYYY-MM-DD"
body: "<formatted markdown content>"
format: "markdown"
Step 6: Confirm to User
After creation, respond with:
✅ 会议纪要已创建！
📄 **[会议纪要：主题 - 日期](文档链接)**
📚 已归档到：「团队知识库名称」
### 摘要
- 共讨论 X 个议题
- 形成 X 项决议
- 产生 X 个待办事项
Guidelines
- Default to Chinese for the document content
- Use emoji sparingly in section headers for visual scanning — as shown in the template
- Keep the document well-structured; prefer tables for action items
- If the user provides audio transcription, clean up filler words and organize by topic
- Preserve the user's original wording for decisions and action items — don't paraphrase important commitments
- This skill saves to group repos — for personal repos, use
personal-meeting-notes
Error Handling
| Situation | Action |
|---|---|
| User provides very little info | Ask for at least: topic, attendees, key decisions |
yuque_list_repos returns empty |
Ask user to verify group login and group Token |
yuque_create_doc fails (403) |
Tell user they may lack write permission; check group Token scope |
yuque_create_doc fails (other) |
Show error, suggest user check yuque-mcp connection |
| No clear action items | Still create the doc, note "This meeting has no clear action items" |
| User wants to save to personal repo | Suggest using personal-meeting-notes skill instead |
| Group login not provided | Ask user for the team's group login |
| Team Token not configured | Inform user that group repos require a team-level Token |