yuque-personal-style-extract

yuque/yuque-plugin · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/yuque/yuque-plugin --skill yuque-personal-style-extract
0 commentsdiscussion
summary

Analyze one or more Yuque documents to extract writing style characteristics, helping users learn from excellent documents or maintain consistent writing style.

skill.md

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 documents
  • yuque_get_doc — Read full document content for style analysis
  • yuque_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-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
how to use yuque-personal-style-extract

How to use yuque-personal-style-extract on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add yuque-personal-style-extract
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/yuque/yuque-plugin --skill yuque-personal-style-extract

The skills CLI fetches yuque-personal-style-extract from GitHub repository yuque/yuque-plugin and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/yuque-personal-style-extract

Reload or restart Cursor to activate yuque-personal-style-extract. Access the skill through slash commands (e.g., /yuque-personal-style-extract) or your agent's skill management interface.

Security & Verification Notice

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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

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

Competitive Analysis

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

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

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

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ 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.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.555 reviews
  • Meera Abbas· Dec 20, 2024

    yuque-personal-style-extract has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Ren Robinson· Dec 20, 2024

    yuque-personal-style-extract is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Nia Chen· Dec 20, 2024

    Useful defaults in yuque-personal-style-extract — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Luis Gill· Dec 12, 2024

    I recommend yuque-personal-style-extract for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Sakshi Patil· Nov 11, 2024

    yuque-personal-style-extract is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Sakura Yang· Nov 11, 2024

    yuque-personal-style-extract fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Sakura Sharma· Nov 11, 2024

    Registry listing for yuque-personal-style-extract matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Luis Mensah· Nov 3, 2024

    yuque-personal-style-extract reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Kofi Haddad· Oct 22, 2024

    Registry listing for yuque-personal-style-extract matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Chaitanya Patil· Oct 2, 2024

    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

1 / 6