yuque-personal-style-extract
8
总安装量
6
周安装量
#34295
全站排名
安装命令
npx skills add https://github.com/yuque/yuque-plugin --skill yuque-personal-style-extract
Agent 安装分布
codex
6
claude-code
6
mcpjam
1
kilo
1
windsurf
1
zencoder
1
Skill 文档
Style Extract â Yuque Document Writing Style Analysis
Analyze one or more Yuque documents to extract writing style characteristics, helping users learn from excellent documents or maintain consistent writing style.
When to Use
- User wants to analyze the writing style of a specific document
- User says “åæä¸ä¸è¿ç¯ææ¡£çåä½é£æ ¼”, “extract the style”, “å¦ä¹ è¿ç¯ææ¡£ç飿 ¼”
- User wants to maintain consistent style across documents
- User says “å¸®ææ»ç»ä¸ä¸æçåä½ç¹ç¹”, “ææ³ä¿æåè¿ç¯ä¸æ ·ç飿 ¼”
Required MCP Tools
All tools are from the yuque-mcp server:
yuque_searchâ Search documents by keyword to find target documentsyuque_get_docâ Read full document content for style analysisyuque_list_reposâ List personal knowledge bases to browse documents
Workflow
Step 1: Identify Target Documents
The user may provide:
- A specific document title or link
- A keyword to search for the document
- A request to analyze their overall writing style (multiple docs)
If a specific document is given:
Tool: yuque_get_doc
Parameters:
repo_id: "<namespace>"
doc_id: "<slug>"
If the user gives keywords, search first:
Tool: yuque_search
Parameters:
query: "<keywords>"
type: "doc"
For overall style analysis, read 3-5 recent documents from the user’s repos.
Step 2: Analyze Style Dimensions
Examine the document(s) across these dimensions:
| Dimension | What to Look For |
|---|---|
| ð ç»æ (Structure) | Heading hierarchy, section organization, use of lists vs paragraphs |
| ð¯ è¯æ° (Tone) | Formal/informal, technical/conversational, authoritative/collaborative |
| ð ç¨è¯ (Vocabulary) | Technical depth, jargon usage, Chinese/English mixing patterns |
| ð ç¯å¹ (Length) | Average section length, paragraph density, overall document length |
| ð¨ æ ¼å¼ (Formatting) | Use of tables, code blocks, images, callouts, emoji |
| ð å¼ç¨ (References) | How sources are cited, use of links, cross-references |
| ð¡ 表达 (Expression) | Use of examples, analogies, rhetorical questions, humor |
Step 3: Extract Style Profile
Compose a style profile with concrete examples:
## ð åä½é£æ ¼åææ¥å
### ææ¡£ä¿¡æ¯
- **ææ¡£**ï¼[æ é¢](龿¥)
- **ç¥è¯åº**ï¼ãç¥è¯åºåç§°ã
- **åæ°**ï¼çº¦ X å
- **æ´æ°æ¶é´**ï¼YYYY-MM-DD
---
### ð ç»æç¹å¾
- **å±çº§**ï¼[å¦ï¼ä½¿ç¨ H2/H3 两级æ é¢ï¼ä¸ä½¿ç¨ H4]
- **ç»ç»æ¹å¼**ï¼[å¦ï¼æ»åæ»ç»æï¼å
ç»ç»è®ºåå±å¼]
- **段è½é¿åº¦**ï¼[å¦ï¼æ¯æ®µ 2-4 å¥ï¼ç®æ´æäº]
### ð¯ è¯æ°ä¸é£æ ¼
- **æ´ä½åºè°**ï¼[å¦ï¼ä¸ä¸ä½ä¸å»æ¿ï¼å¶å°ä½¿ç¨å£è¯å表达]
- **人称使ç¨**ï¼[å¦ï¼å¤ç¨"æä»¬"ï¼è¥é å使]
- **å
¸åå¥å¼**ï¼[å¼ç¨ 1-2 个代表æ§å¥å]
### ð ç¨è¯ç¹ç¹
- **æ¯è¯å¯åº¦**ï¼[é«/ä¸/ä½]
- **ä¸è±æ··ç¨**ï¼[å¦ï¼ææ¯åè¯ä¿çè±æï¼å
¶ä½ç¨ä¸æ]
- **é«é¢è¯æ±**ï¼[ååº 5-8 个ç¹å¾æ§è¯æ±]
### ð¨ æ ¼å¼å好
- **常ç¨å
ç´ **ï¼[å¦ï¼å¤§é使ç¨è¡¨æ ¼ã代ç åè¾å°ã忬¢ç¨ emoji åæ è®°]
- **è§è§èå¥**ï¼[å¦ï¼æ¯ 2-3 段æå
¥ä¸ä¸ªå表æè¡¨æ ¼ï¼é¿å
大段纯æå]
### ð¡ è¡¨è¾¾ææ³
- **䏾便¹å¼**ï¼[å¦ï¼å欢ç¨å®é
åºæ¯ä¸¾ä¾ï¼å¸¸ç¨"æ¯å¦è¯´..."]
- **é»è¾è¿æ¥**ï¼[å¦ï¼åç¨"é¦å
/å
¶æ¬¡/æå"ï¼è¿æ¸¡èªç¶]
---
### ð¯ 飿 ¼æè¦ï¼ä¸å¥è¯ï¼
> [ç¨ä¸å¥è¯æ¦æ¬è¿ä¸ªåä½é£æ ¼ï¼å¦ï¼"ä¸ä¸ä¸¥è°¨ä½ä¸å¤±äº²ååçææ¯ææ¡£é£æ ¼ï¼åç¨ç»æå表达åå®ä¾è¯´æã"]
### ð 飿 ¼å¤ç¨å»ºè®®
å¦æä½ æ³æ¨¡ä»¿è¿ä¸ªé£æ ¼åä½ï¼æ³¨æä»¥ä¸è¦ç¹ï¼
1. [å
·ä½å»ºè®® 1]
2. [å
·ä½å»ºè®® 2]
3. [å
·ä½å»ºè®® 3]
Step 4: Compare Styles (Optional)
If the user provides multiple documents for comparison:
## ð 飿 ¼å¯¹æ¯
| 维度 | ææ¡£ A | ææ¡£ B |
|------|--------|--------|
| è¯æ° | [ç¹å¾] | [ç¹å¾] |
| ç»æ | [ç¹å¾] | [ç¹å¾] |
| ç¨è¯ | [ç¹å¾] | [ç¹å¾] |
| æ ¼å¼ | [ç¹å¾] | [ç¹å¾] |
### å
±åç¹
- [å
±åç¹å¾ 1]
- [å
±åç¹å¾ 2]
### å·®å¼ç¹
- [å·®å¼ 1]
- [å·®å¼ 2]
Guidelines
- Always answer in the same language the user used (Chinese or English)
- Use concrete examples from the actual document â quote specific sentences or patterns
- Be objective and descriptive, not judgmental â “uses short paragraphs” not “paragraphs are too short”
- When analyzing multiple documents, identify both consistent patterns and variations
- The style profile should be actionable â someone should be able to write in a similar style after reading it
- This skill analyzes documents in personal repos â for team repos, use the corresponding skill in the
yuque-groupplugin
Error Handling
| Situation | Action |
|---|---|
| Document not found | Try alternative search keywords, then inform user |
| Document too short (<100 chars) | Inform user the document is too short for meaningful style analysis |
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 |
| User provides no specific document | List recent docs from their repos and ask which to analyze |