Analyze one or more Yuque documents to extract writing style characteristics, helping users learn from excellent documents or maintain consistent writing style.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionyuque-personal-style-extractExecute the skills CLI command in your project's root directory to begin installation:
Fetches yuque-personal-style-extract from yuque/yuque-plugin and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate yuque-personal-style-extract. Access via /yuque-personal-style-extract in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
67
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
67
stars
Analyze one or more Yuque documents to extract writing style characteristics, helping users learn from excellent documents or maintain consistent writing style.
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 documentsThe user may provide:
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.
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 |
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]
If the user provides multiple documents for comparison:
## 📊 风格对比
| 维度 | 文档 A | 文档 B |
|------|--------|--------|
| 语气 | [特征] | [特征] |
| 结构 | [特征] | [特征] |
| 用词 | [特征] | [特征] |
| 格式 | [特征] | [特征] |
### 共同点
- [共同特征 1]
- [共同特征 2]
### 差异点
- [差异 1]
- [差异 2]
yuque-group plugin| 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 |
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
yuque-personal-style-extract has been reliable in day-to-day use. Documentation quality is above average for community skills.
yuque-personal-style-extract is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in yuque-personal-style-extract — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend yuque-personal-style-extract for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
yuque-personal-style-extract is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
yuque-personal-style-extract fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for yuque-personal-style-extract matched our evaluation — installs cleanly and behaves as described in the markdown.
yuque-personal-style-extract reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for yuque-personal-style-extract matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: yuque-personal-style-extract is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 55