Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

$pwd:

meeting-notes

Name: Meeting Notes
Author: yuque

// 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.

Executar no Manus

$ git log --oneline --stat

stars:178

forks:19

updated:3 de abril de 2026 às 09:20

SKILL.md

readonly

name	meeting-notes
description	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.
license	Apache-2.0
compatibility	Requires yuque-mcp server connected to a Yuque account with group Token (group-level access)
metadata	{"author":"chen201724","version":"2.0"}

Meeting Notes — Format and Archive to Team Yuque

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 "帮我整理会议纪要到团队库", "save meeting notes to group repo", "把会议记录存到团队知识库"
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_books — List group knowledge bases to find the target repo
yuque_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
会议主题 (Topic)	Yes	"Q1 产品规划评审"
会议日期 (Date)	Yes (default: today)	"2024-01-15"
会议时间 (Time)	No	"14:00-15:30"
参会人员 (Attendees)	Yes	"张三、李四、王五"
主持人 (Host)	No	"张三"
记录人 (Recorder)	No	"AI 助手"
团队标识 (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: "请告诉我团队的语雀团队标识（group login），我来把会议纪要存到团队知识库。"

Step 2: Structure the Content

Organize the meeting content into these sections:

议题 (Agenda Items) — What was discussed
讨论要点 (Discussion Points) — Key arguments, opinions, data shared
决议 (Decisions) — What was decided
待办事项 (Action Items) — Who does what by when
备注 (Notes) — Anything else worth recording

For each action item, ensure it has:

负责人 (Owner): Who is responsible
截止日期 (Deadline): When it's due
具体内容 (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_books
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 "会议纪要" or "Meeting Notes" repo, suggest it
If the user says "就放那个会议的库", 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 the meeting-notes skill in the yuque-personal plugin

Error Handling

Situation	Action
User provides very little info	Ask for at least: topic, attendees, key decisions
`yuque_list_books` 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 "本次会议无明确待办事项"
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

related-skills.json

mesmo repositório

daily-capture.md

from "yuque/yuque-ecosystem"

Collect fleeting ideas and thoughts throughout the day, then periodically organize them into structured thematic notes in your Yuque knowledge base. For personal/individual use.

2026-04-03178

knowledge-connect.md

from "yuque/yuque-ecosystem"

Analyze documents in your Yuque knowledge base, discover hidden connections between them (similar topics, complementary content), and suggest cross-reference links to build a knowledge network. For personal/individual use.

2026-04-03178

reading-digest.md

from "yuque/yuque-ecosystem"

Extract core insights, golden quotes, and action items from articles, then generate structured reading notes and save them to a specified Yuque knowledge base. For personal/individual use.

2026-04-03178

smart-summary.md

from "yuque/yuque-ecosystem"

Generate summaries of any Yuque document or knowledge base at different granularity levels — one-liner, key points, or detailed summary. For personal/individual use.

2026-04-03178

stale-detector.md

from "yuque/yuque-ecosystem"

Scan a Yuque knowledge base to find stale or potentially outdated documents, analyze their relevance, and generate a maintenance report with update or archive recommendations. For personal/individual use.

2026-04-03178

style-extract.md

from "yuque/yuque-ecosystem"

Analyze a user's writing style from their Yuque documents — vocabulary habits, sentence patterns, tone characteristics — and generate a style profile that can be used to maintain consistent voice when writing new content. For personal/individual use.

2026-04-03178

package.json

"author": "yuque"

"repository": "yuque/yuque-ecosystem"

Abrir repositório GitHub Ver repositórios do creator

$ install --global

$ download --local

Executar no Manus

$ useful --forSOC

Secretárias e assistentes administrativos (exceto jurídico, médico e executivo)Escritório e Suporte Administrativo43-6014L4

name	meeting-notes
description	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.
license	Apache-2.0
compatibility	Requires yuque-mcp server connected to a Yuque account with group Token (group-level access)
metadata	{"author":"chen201724","version":"2.0"}

Meeting Notes — Format and Archive to Team Yuque

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 "帮我整理会议纪要到团队库", "save meeting notes to group repo", "把会议记录存到团队知识库"
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_books — List group knowledge bases to find the target repo
yuque_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
会议主题 (Topic)	Yes	"Q1 产品规划评审"
会议日期 (Date)	Yes (default: today)	"2024-01-15"
会议时间 (Time)	No	"14:00-15:30"
参会人员 (Attendees)	Yes	"张三、李四、王五"
主持人 (Host)	No	"张三"
记录人 (Recorder)	No	"AI 助手"
团队标识 (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: "请告诉我团队的语雀团队标识（group login），我来把会议纪要存到团队知识库。"

Step 2: Structure the Content

Organize the meeting content into these sections:

议题 (Agenda Items) — What was discussed
讨论要点 (Discussion Points) — Key arguments, opinions, data shared
决议 (Decisions) — What was decided
待办事项 (Action Items) — Who does what by when
备注 (Notes) — Anything else worth recording

For each action item, ensure it has:

负责人 (Owner): Who is responsible
截止日期 (Deadline): When it's due
具体内容 (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_books
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 "会议纪要" or "Meeting Notes" repo, suggest it
If the user says "就放那个会议的库", 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 the meeting-notes skill in the yuque-personal plugin

Error Handling

Situation	Action
User provides very little info	Ask for at least: topic, attendees, key decisions
`yuque_list_books` 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 "本次会议无明确待办事项"
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

meeting-notes

Meeting Notes — Format and Archive to Team Yuque

When to Use

Required MCP Tools

Workflow

Step 1: Gather Meeting Information

Step 2: Structure the Content

Step 3: Format the Document

Step 4: Find Team Repository

Step 5: Create the Document

Step 6: Confirm to User

Guidelines

Error Handling

Mais deste repositório

Mais deste repositório

Meeting Notes — Format and Archive to Team Yuque

When to Use

Required MCP Tools

Workflow

Step 1: Gather Meeting Information

Step 2: Structure the Content

Step 3: Format the Document

Step 4: Find Team Repository

Step 5: Create the Document

Step 6: Confirm to User

Guidelines

Error Handling