yuque-personal-note-refine
8
总安装量
3
周安装量
#35303
全站排名
安装命令
npx skills add https://github.com/yuque/yuque-plugin --skill yuque-personal-note-refine
Agent 安装分布
codex
3
claude-code
3
Skill 文档
Note Refine â Restructure & Polish Your Notes
Help the user transform scattered, rough notes into well-structured, deduplicated, and enriched documents. Turn chaos into clarity.
When to Use
- User wants to clean up messy notes
- User says “å¸®ææ´çç¬è®°”, “refine my notes”, “æè¿äºç¬è®°çä¸ä¸”
- User has accumulated daily captures and wants to consolidate them
- User says “è¿äºç¬è®°å¤ªä¹±äº”, “帮æéæ°ç»ç»ä¸ä¸”, “å»éæ´ç”
Required MCP Tools
All tools are from the yuque-mcp server:
yuque_searchâ Find the target notes to refineyuque_get_docâ Read the full content of notesyuque_list_reposâ List personal reposyuque_list_docsâ List documents in a repoyuque_create_docâ Create the refined documentyuque_update_docâ Update the original document in place
Workflow
Step 1: Identify the Source Notes
The user may provide:
- A specific document to refine
- A date range of daily captures to consolidate
- A topic keyword to find related scattered notes
- Multiple document references to merge
If the user says “æ´çææè¿çç¬è®°”:
Tool: yuque_search
Parameters:
query: "æ¯æ¥æè·"
type: "doc"
Or for topic-specific notes:
Tool: yuque_search
Parameters:
query: "<topic keyword>"
type: "doc"
Step 2: Read All Source Notes
For each identified document:
Tool: yuque_get_doc
Parameters:
repo_id: "<namespace>"
doc_id: "<slug>"
Read up to 5-10 source documents. If there are more, prioritize by recency and relevance.
Step 3: Analyze and Plan
Before refining, analyze the raw content:
- Identify themes â Group related content by topic
- Find duplicates â Flag repeated ideas or information
- Spot gaps â Note where information is incomplete
- Assess structure â Determine the best organizational approach
Present the analysis to the user:
## ð ç¬è®°åæ
**æ¥æº**ï¼X ç¯ææ¡£ï¼å
±çº¦ XXXX å
### 主é¢åå¸
- **[ä¸»é¢ 1]**ï¼X æ¡ç¸å
³è®°å½
- **[ä¸»é¢ 2]**ï¼X æ¡ç¸å
³è®°å½
- **[ä¸»é¢ 3]**ï¼X æ¡ç¸å
³è®°å½
### åç°
- ð åç° X å¤éå¤å
容
- ð³ï¸ åç° X å¤ä¿¡æ¯ç¼ºå£
- ð 建议æ´ç为 X ç¯ä¸»é¢ææ¡£
è¦æè¿ä¸ªæ¹åæ´çåï¼
Step 4: Refine the Notes
Based on user confirmation, perform the refinement:
4a. Single Document Refinement
Restructure one document:
- Add clear headings and hierarchy
- Remove duplicate content
- Improve wording and clarity
- Add missing context or transitions
- Organize chronological notes into logical structure
4b. Multi-Document Consolidation
Merge multiple notes into themed documents:
- Group by topic
- Deduplicate across documents
- Create a coherent narrative
- Preserve attribution (note original dates/sources)
Refined document template:
# [䏻颿 é¢]
> æ´çèª X ç¯ç¬è®°ï¼æ¶é´è·¨åº¦ï¼YYYY-MM-DD è³ YYYY-MM-DD
> æåæ´çï¼YYYY-MM-DD
---
## æ¦è¿°
[对è¿ä¸ªä¸»é¢çæ´ä½æ¦è¿°ï¼2-3 å¥è¯]
---
## [åç±» 1]
### [åä¸»é¢ 1.1]
[æ´çåçå
容]
### [åä¸»é¢ 1.2]
[æ´çåçå
容]
---
## [åç±» 2]
### [åä¸»é¢ 2.1]
[æ´çåçå
容]
---
## å¾
è¡¥å
- [ ] [è¯å«åºçä¿¡æ¯ç¼ºå£ 1]
- [ ] [è¯å«åºçä¿¡æ¯ç¼ºå£ 2]
---
## åå§æ¥æº
- [åææ¡£ 1 æ é¢](龿¥) â YYYY-MM-DD
- [åææ¡£ 2 æ é¢](龿¥) â YYYY-MM-DD
---
> æ¬ææ¡£ç± AI 婿æ´çï¼åå§ç¬è®°å·²ä¿çã
Step 5: Save the Refined Document
Ask the user’s preference:
- Create new â Save as a new document (recommended for multi-doc consolidation)
- Update in place â Replace the original document (for single doc refinement)
For new document:
Tool: yuque_create_doc
Parameters:
repo_id: "<namespace>"
title: "[䏻颿 é¢]"
body: "<refined content>"
format: "markdown"
For in-place update:
Tool: yuque_update_doc
Parameters:
repo_id: "<namespace>"
doc_id: "<slug>"
body: "<refined content>"
Step 6: Confirm
â
ç¬è®°æ´ç宿ï¼
ð **[[䏻颿 é¢]](ææ¡£é¾æ¥)**
ð å·²ä¿åå°ï¼ãç¥è¯åºåç§°ã
### æ´çææ
- ð¥ è¾å
¥ï¼X ç¯åå§ç¬è®°ï¼çº¦ XXXX å
- ð¤ è¾åºï¼1 ç¯ç»æåææ¡£ï¼çº¦ XXXX å
- ð å»é¤éå¤ï¼X å¤
- ð³ï¸ æ è®°å¾
è¡¥å
ï¼X å¤
ð¡ åå§ç¬è®°å·²ä¿çï¼å¯éæ¶å¯¹ç
§ã
Guidelines
- Always preserve the original notes â refine into a new document by default
- Don’t discard information during deduplication; merge and enrich instead
- Maintain the user’s voice and terminology â don’t over-formalize casual notes
- Flag uncertain interpretations with “ãå¾ ç¡®è®¤ã” markers
- For daily captures, suggest a weekly or bi-weekly refinement cadence
- If notes span multiple topics, create separate refined documents per topic
- Add a “å¾ è¡¥å ” section for identified gaps â this helps the user know what to add later
- Default language is Chinese
Error Handling
| Situation | Action |
|---|---|
| Source notes are too few (<3 items) | Refine what’s available; suggest capturing more first |
| Source notes are too many (>10 docs) | Focus on most recent or ask user to narrow the scope |
| Content is already well-structured | Tell user honestly; suggest minor improvements only |
yuque_update_doc fails |
Fall back to creating a new document |
| Mixed languages in notes | Maintain the dominant language; don’t force translation |