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:
## ๐ ้ฃๆ ผๅฏนๆฏ
|------|--------|--------|
| ่ฏญๆฐ | [็นๅพ] | [็นๅพ] |
| ็ปๆ | [็นๅพ] | [็นๅพ] |
| ็จ่ฏ | [็นๅพ] | [็นๅพ] |
| ๆ ผๅผ | [็นๅพ] | [็นๅพ] |
### ๅ
ฑๅ็น
- [ๅ
ฑๅ็นๅพ 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-group plugin
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 |
