yuque-personal-smart-summary▌
yuque/yuque-plugin · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Generate intelligent summaries for an entire knowledge base or a set of documents, helping users quickly understand content landscape, key themes, and important insights.
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 |
How to use yuque-personal-smart-summary on Cursor
AI-first code editor with Composer
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-smart-summary
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches yuque-personal-smart-summary from GitHub repository yuque/yuque-plugin and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate yuque-personal-smart-summary. Access the skill through slash commands (e.g., /yuque-personal-smart-summary) 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
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.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 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▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★29 reviews- ★★★★★Valentina Okafor· Dec 28, 2024
yuque-personal-smart-summary fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Dhruvi Jain· Dec 12, 2024
Keeps context tight: yuque-personal-smart-summary is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Anaya Lopez· Dec 12, 2024
We added yuque-personal-smart-summary from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Valentina Gupta· Dec 8, 2024
Useful defaults in yuque-personal-smart-summary — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Omar Park· Nov 19, 2024
Registry listing for yuque-personal-smart-summary matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Oshnikdeep· Nov 3, 2024
yuque-personal-smart-summary has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Arjun Lopez· Nov 3, 2024
yuque-personal-smart-summary reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Ganesh Mohane· Oct 22, 2024
Solid pick for teams standardizing on skills: yuque-personal-smart-summary is focused, and the summary matches what you get after install.
- ★★★★★Arjun Chawla· Oct 22, 2024
Registry listing for yuque-personal-smart-summary matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Omar Ndlovu· Oct 10, 2024
yuque-personal-smart-summary reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 29