yuque-personal-smart-summary
npx skills add https://github.com/yuque/yuque-plugin --skill yuque-personal-smart-summary
Agent 安装分布
Skill 文档
Smart Summary â Yuque Knowledge Base & Document Summarization
Generate intelligent summaries for an entire knowledge base or a set of documents, helping users quickly understand content landscape, key themes, and important insights.
When to Use
- User wants an overview of a knowledge base
- User says “å¸®ææ»ç»ä¸ä¸è¿ä¸ªç¥è¯åº”, “summarize my repo”, “è¿ä¸ªåºé齿ä»ä¹”
- User wants a summary of multiple related documents
- User says “帮æå个ç¥è¯çç¹”, “generate a project summary from my docs”
- User wants periodic knowledge review
Required MCP Tools
All tools are from the yuque-mcp server:
yuque_list_reposâ List personal knowledge basesyuque_get_repo_tocâ Get the table of contents of a knowledge baseyuque_get_docâ Read full document contentyuque_searchâ Search documents by keyword (for topic-based summaries)
Workflow
Step 1: Identify Scope
Determine what the user wants summarized:
Option A: Entire knowledge base
Tool: yuque_list_repos
Parameters:
type: "user"
Then let the user pick a repo, or use the one they specified.
Option B: Specific topic across repos
Tool: yuque_search
Parameters:
query: "<topic keywords>"
type: "doc"
Option C: User specifies exact documents Proceed directly to reading them.
Step 2: Get Document List
For a knowledge base summary, get the table of contents:
Tool: yuque_get_repo_toc
Parameters:
repo_id: "<namespace>"
This gives you the full structure â titles, hierarchy, and document slugs.
Step 3: Sample and Read Documents
For large knowledge bases (>20 docs), use a sampling strategy:
- Read all documents if â¤10 docs
- Sample strategically if >10 docs:
- Read the top-level / introductory documents first
- Pick 2-3 documents from each major section
- Prioritize recently updated documents
- Read up to 10-15 documents total
Tool: yuque_get_doc
Parameters:
repo_id: "<namespace>"
doc_id: "<slug>"
Step 4: Analyze and Categorize
As you read, track:
- Main themes â What topics are covered
- Content types â Tutorials, references, notes, specs, etc.
- Coverage depth â Which areas are well-documented vs sparse
- Freshness â How recently content was updated
- Connections â How documents relate to each other
Step 5: Generate Summary
Compose the summary in the following format:
## ð ç¥è¯åºæè¦ï¼ãç¥è¯åºåç§°ã
### æ¦è§
- **ææ¡£æ»æ°**ï¼X ç¯
- **æè¿æ´æ°**ï¼YYYY-MM-DD
- **主è¦è¯è¨**ï¼ä¸æ/è±æ/æ··å
---
### ðï¸ å
å®¹ç»æ
ç¥è¯åºå
å«ä»¥ä¸ä¸»è¦æ¿åï¼
1. **[æ¿ååç§°]**ï¼X ç¯ææ¡£ï¼
- [ç®è¦æè¿°è¿ä¸ªæ¿åçå
容]
- ä»£è¡¨ææ¡£ï¼[ææ¡£æ é¢](龿¥)
2. **[æ¿ååç§°]**ï¼X ç¯ææ¡£ï¼
- [ç®è¦æè¿°]
- ä»£è¡¨ææ¡£ï¼[ææ¡£æ é¢](龿¥)
3. **[æ¿ååç§°]**ï¼X ç¯ææ¡£ï¼
- [ç®è¦æè¿°]
- ä»£è¡¨ææ¡£ï¼[ææ¡£æ é¢](龿¥)
---
### ð æ ¸å¿è¦ç¹
仿´ä¸ªç¥è¯åºä¸æç¼çå
³é®ä¿¡æ¯ï¼
1. **[è¦ç¹ 1]**ï¼[2-3 å¥è¯æ¦æ¬]
2. **[è¦ç¹ 2]**ï¼[2-3 å¥è¯æ¦æ¬]
3. **[è¦ç¹ 3]**ï¼[2-3 å¥è¯æ¦æ¬]
4. **[è¦ç¹ 4]**ï¼[2-3 å¥è¯æ¦æ¬]
5. **[è¦ç¹ 5]**ï¼[2-3 å¥è¯æ¦æ¬]
---
### ð ç¥è¯åºå¥åº·åº¦
| ææ | ç¶æ |
|------|------|
| å
容è¦ç | [å
¨é¢/æç¼ºå£/å¾
è¡¥å
] |
| æ´æ°é¢ç | [æ´»è·/ä¸è¬/è¾å°æ´æ°] |
| ç»ææ¸
æ°åº¦ | [æ¸
æ°/ä¸è¬/éè¦æ´ç] |
| ææ¡£è´¨é | [é«/ä¸/åå·®ä¸é½] |
---
### ð¡ 建议
- [建议 1ï¼å¦"XX æ¿åå
容è¾å°ï¼å»ºè®®è¡¥å
"]
- [建议 2ï¼å¦"é¨åææ¡£è¶
è¿ 6 ä¸ªææªæ´æ°ï¼å»ºè®®æ£æ¥æ¶ææ§"]
- [建议 3ï¼å¦"建议添å ä¸ç¯æ»è§ææ¡£ä¸²èåæ¿å"]
Step 6: Multi-Document Summary (Alternative)
If summarizing specific documents rather than a whole repo:
## ð ææ¡£æè¦
### ææ¡£å表
| # | æ é¢ | ç¥è¯åº | æ´æ°æ¶é´ |
|---|------|--------|----------|
| 1 | [æ é¢](龿¥) | ãåºåã | YYYY-MM-DD |
| 2 | [æ é¢](龿¥) | ãåºåã | YYYY-MM-DD |
### 综åæè¦
[3-5 段è¯ï¼ç»¼åææææ¡£çæ ¸å¿å
容ï¼çªåºå
±å主é¢åå
³é®ä¿¡æ¯]
### åææ¡£è¦ç¹
#### 1. [ææ¡£æ é¢]
- [è¦ç¹ 1]
- [è¦ç¹ 2]
- [è¦ç¹ 3]
#### 2. [ææ¡£æ é¢]
- [è¦ç¹ 1]
- [è¦ç¹ 2]
- [è¦ç¹ 3]
### ææ¡£é´å
³è
- [ææ¡£ A åææ¡£ B å¨ XX æ¹é¢äºç¸è¡¥å
]
- [ææ¡£ C æ¯ææ¡£ A çæ·±å
¥å±å¼]
Guidelines
- Always answer in the same language the user used (Chinese or English)
- For large knowledge bases, be upfront about sampling: “ç¥è¯åºå ±æ X ç¯ææ¡£ï¼ææ½æ ·é è¯»äº Y ç¯è¿è¡åæ”
- Focus on actionable insights, not just listing document titles
- Highlight gaps and opportunities â what’s missing is as valuable as what’s there
- Include document links so users can dive deeper into any topic
- This skill summarizes personal repos â for team repos, use the corresponding skill in the
yuque-groupplugin
Error Handling
| Situation | Action |
|---|---|
yuque_list_repos returns empty |
Ask user for the exact repo name or ID |
yuque_get_repo_toc returns empty |
Inform user the knowledge base appears to be empty |
yuque_get_doc fails (404) |
Skip this doc, note it may have been deleted |
yuque_get_doc fails (403) |
Tell user they may lack permission to access this doc |
| API timeout | Retry once, then inform user of connectivity issue |
| Knowledge base has >50 docs | Sample 10-15 docs, clearly state the sampling approach |