Help the user quickly capture ideas, thoughts, meeting insights, reading annotations, and any fleeting information into their personal Yuque knowledge base with minimal friction.
When to Use
- User wants to quickly jot down an idea or thought
- User says "note this down", "help me record", "capture this", "write a note"
- User shares a fleeting thought, inspiration, or meeting insight
- User says "jot down this idea first", "quick note", "quick capture"
Required MCP Tools
All tools are from the yuque-mcp server:
yuque_list_repos— List personal repos to find the capture targetyuque_search— (Optional) Find today's capture doc if appendingyuque_list_docs— (Optional) Check if today's daily note existsyuque_create_doc— Create a new capture documentyuque_update_doc— Append to an existing capture document
Workflow
Step 1: Receive the Capture
The user's input can be:
- A raw idea or thought (1-2 sentences)
- A longer note with context
- A quote or snippet from something they read
- A meeting insight or action item
- A mix of the above
Classify the capture type:
| Type | Icon | Example |
|---|---|---|
| 💡 Idea/Inspiration | 💡 | "Suddenly thought we could use Redis for caching" |
| 📝 Note | 📝 | "Today I learned how to use Go's context..." |
| 📖 Reading Annotation | 📖 | "The point mentioned in this article is quite interesting..." |
| 🎯 To-do/Action | 🎯 | "Remember to follow up on the API design review next week" |
| 💬 Meeting Inspiration | 💬 | "The architecture plan discussed in the meeting is worth exploring further..." |
| 🔗 Link/Resource | 🔗 | "This tool is great:https://..." |
Step 2: Determine Capture Strategy
Two strategies based on user preference:
Strategy A: Daily Note (Default)
Append to today's daily capture document. If it doesn't exist, create one.
Strategy B: Standalone Note
Create a separate document for this capture (for longer or topic-specific notes).
If the user's input is short (< 100 words), default to Strategy A. If longer or clearly a standalone topic, use Strategy B. Ask if unclear.
Step 3A: Daily Note — Append Mode
Check if today's daily note exists:
Tool: yuque_search
Parameters:
query: "每日捕获 YYYY-MM-DD"
type: "doc"
If found, append to it:
Tool: yuque_update_doc
Parameters:
repo_id: "<namespace>"
doc_id: "<slug>"
body: "<existing content>\n\n---\n\n### [HH:MM] [类型图标] [简短标题]\n\n[捕获内容]\n"
If not found, create today's daily note:
Tool: yuque_create_doc
Parameters:
repo_id: "<namespace>"
title: "📥 每日捕获 YYYY-MM-DD"
body: "<daily note template with first capture>"
format: "markdown"
Daily note template:
# 📥 每日捕获 YYYY-MM-DD
> 今日碎片化记录,定期整理归档。
---
### [HH:MM] [类型图标] [简短标题]
[捕获内容]
[标签:#tag1 #tag2]
Step 3B: Standalone Note
Tool: yuque_list_repos
Parameters:
type: "user"
Tool: yuque_create_doc
Parameters:
repo_id: "<namespace>"
title: "[类型图标] [标题]"
body: "<formatted note>"
format: "markdown"
Step 4: Confirm
For daily note append:
✅ 已捕获!
[类型图标] **[简短标题]** → 已追加到「📥 每日捕获 YYYY-MM-DD」
💡 今日已捕获 X 条记录。
For standalone note:
✅ 笔记已创建!
📄 **[[类型图标] 标题](文档链接)**
📚 已保存到:「知识库名称」
Guidelines
- Speed is everything — minimize questions, maximize capture
- If the user just throws a sentence at you, capture it immediately; don't ask for clarification
- Auto-generate a short title from the content if the user doesn't provide one
- Add relevant tags based on content analysis (e.g., #tech, #product, #inspiration)
- Keep the formatting lightweight — this is a quick capture, not a polished document
- Default to daily note append mode for short captures
- Suggest periodic review: "Your daily captures have accumulated quite a bit—would you like to organize them?" (link to note-refine skill)
- Default language is Chinese
Error Handling
| Situation | Action |
|---|---|
| No capture repo found | Ask user which repo to use, or suggest creating a "Quick Notes" repo |
yuque_update_doc fails |
Fall back to creating a new standalone note |
yuque_search can't find today's note |
Create a new daily note document |
| User input is ambiguous | Capture as-is with 📝 type; don't over-classify |
| Very long input (>500 words) | Switch to standalone note strategy automatically |