yuque-personal-knowledge-connect▌
yuque/yuque-plugin · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Help the user discover hidden connections between their documents, find related content, and build a knowledge network with bidirectional links across their personal Yuque knowledge base.
Knowledge Connect — Discover Document Relationships & Build Knowledge Networks
Help the user discover hidden connections between their documents, find related content, and build a knowledge network with bidirectional links across their personal Yuque knowledge base.
When to Use
- User wants to find documents related to a specific topic
- User says "有哪些相关文档", "find related docs", "帮我建立知识关联"
- User wants to build a knowledge map or graph for a topic
- User says "这个主题还有哪些相关的", "帮我串联一下知识", "构建知识图谱"
Required MCP Tools
All tools are from the yuque-mcp server:
yuque_search— Search for related documents by keywordyuque_get_doc— Read document content to analyze connectionsyuque_list_repos— List personal repos to scanyuque_list_docs— List documents in repos for broader discoveryyuque_update_doc— Add cross-reference links to documentsyuque_create_doc— Create knowledge map documents
Workflow
Step 1: Identify the Starting Point
The user may provide:
- A specific document to find connections for
- A topic or keyword to explore
- A request to map an entire knowledge area
If starting from a document:
Tool: yuque_get_doc
Parameters:
repo_id: "<namespace>"
doc_id: "<slug>"
Extract key concepts, terms, and themes from the document.
Step 2: Discover Related Documents
Search for related content using extracted keywords:
Tool: yuque_search
Parameters:
query: "<keyword 1>"
type: "doc"
Repeat with different keywords to cast a wider net. Use:
- Direct topic keywords
- Synonyms and related terms
- Key people or project names mentioned
- Technical terms and concepts
Also scan repos for broader discovery:
Tool: yuque_list_docs
Parameters:
namespace: "<repo_namespace>"
Step 3: Read and Analyze Connections
For each potentially related document (top 5-10):
Tool: yuque_get_doc
Parameters:
repo_id: "<namespace>"
doc_id: "<slug>"
Analyze the relationship type:
| Relationship | Description | Example |
|---|---|---|
| 🔗 直接相关 | Same topic, different angle | 两篇都讲微服务架构 |
| 🧩 互补 | Fills gaps in each other | 一篇讲设计,一篇讲实现 |
| 📚 前置/后续 | Sequential knowledge | 入门篇 → 进阶篇 |
| 🔀 交叉引用 | Shared concepts across topics | 都提到了 Redis 缓存策略 |
| ⚡ 矛盾/对比 | Conflicting viewpoints | 两篇对同一问题有不同方案 |
Step 4: Build the Knowledge Map
Present the discovered connections:
# 🗺️ 知识关联图:[主题/文档标题]
> 基于「[起始文档]」发现的知识网络
> 扫描范围:X 个知识库,XX 篇文档
> 生成时间:YYYY-MM-DD
---
## 🎯 中心节点
**[起始文档标题](链接)**
- 知识库:[库名]
- 核心概念:[概念1]、[概念2]、[概念3]
---
## 🔗 关联文档
### 直接相关
| 文档 | 知识库 | 关联类型 | 关联说明 |
|------|--------|----------|----------|
| [标题](链接) | [库名] | 🔗 直接相关 | [为什么相关] |
| [标题](链接) | [库名] | 🧩 互补 | [互补点说明] |
### 延伸阅读
| 文档 | 知识库 | 关联类型 | 关联说明 |
|------|--------|----------|----------|
| [标题](链接) | [库名] | 📚 前置知识 | [说明] |
| [标题](链接) | [库名] | 🔀 交叉引用 | [共同概念] |
---
## 🧠 知识网络
[中心文档] ├── 🔗 [直接相关文档 1] │ └── 🔀 [交叉引用文档 A] ├── 🧩 [互补文档 2] ├── 📚 [前置文档 3] │ └── 📚 [更前置文档 B] └── ⚡ [对比文档 4]
---
## 💡 发现与建议
- **知识聚类**:[发现的知识聚类模式]
- **知识缺口**:[发现缺少的关联文档或主题]
- **建议行动**:
1. [建议创建的文档或补充的内容]
2. [建议建立的新关联]
---
> 本知识图谱由 AI 助手自动生成,关联关系基于内容分析。
Step 5: (Optional) Add Cross-References
If the user agrees, add "相关文档" sections to the connected documents:
Tool: yuque_update_doc
Parameters:
repo_id: "<namespace>"
doc_id: "<slug>"
body: "<original content>\n\n---\n\n## 🔗 相关文档\n\n- [相关文档 1](链接) — [关联说明]\n- [相关文档 2](链接) — [关联说明]\n"
Ask before modifying any existing document:
- "要在这些文档中添加相互引用链接吗?"
Step 6: (Optional) Save Knowledge Map
Tool: yuque_create_doc
Parameters:
repo_id: "<namespace>"
title: "🗺️ 知识图谱:[主题]"
body: "<knowledge map content>"
format: "markdown"
Step 7: Confirm
✅ 知识关联分析完成!
🗺️ **发现 X 篇相关文档,建立了 X 个关联**
### 关联概览
- 🔗 直接相关:X 篇
- 🧩 互补文档:X 篇
- 📚 前置/后续:X 篇
- 🔀 交叉引用:X 篇
💡 建议:[最重要的一条建议]
Guidelines
- Start broad, then narrow — search with multiple keywords to find unexpected connections
- Quality over quantity — 5 strong connections are better than 20 weak ones
- Explain why documents are related, not just that they are
- Always ask before modifying existing documents (adding cross-references)
- The knowledge map should be actionable — include specific suggestions for strengthening the knowledge network
- Identify knowledge gaps — what's missing is as valuable as what's connected
- For large knowledge bases, focus on one topic area at a time
- Default language is Chinese
Error Handling
| Situation | Action |
|---|---|
yuque_search returns few results |
Broaden keywords; try synonyms and related terms |
| Starting document has no clear connections | Suggest the document may be on a new topic; offer to search broader |
| Too many connections found (>15) | Prioritize by relevance strength; group into clusters |
yuque_update_doc fails when adding links |
Skip that document; note it in the report |
| User's knowledge base is very small | Acknowledge limited scope; suggest topics to write about to build the network |
How to use yuque-personal-knowledge-connect 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-knowledge-connect
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches yuque-personal-knowledge-connect 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-knowledge-connect. Access the skill through slash commands (e.g., /yuque-personal-knowledge-connect) 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.6★★★★★71 reviews- ★★★★★Henry Brown· Dec 28, 2024
yuque-personal-knowledge-connect has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Camila Ndlovu· Dec 24, 2024
yuque-personal-knowledge-connect reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Mei Brown· Dec 24, 2024
Solid pick for teams standardizing on skills: yuque-personal-knowledge-connect is focused, and the summary matches what you get after install.
- ★★★★★Kabir Ghosh· Dec 24, 2024
Registry listing for yuque-personal-knowledge-connect matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Arjun Martin· Dec 20, 2024
Keeps context tight: yuque-personal-knowledge-connect is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Kofi Kim· Dec 20, 2024
Useful defaults in yuque-personal-knowledge-connect — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Mei Taylor· Dec 16, 2024
Registry listing for yuque-personal-knowledge-connect matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Dhruvi Jain· Dec 8, 2024
I recommend yuque-personal-knowledge-connect for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Oshnikdeep· Nov 27, 2024
Solid pick for teams standardizing on skills: yuque-personal-knowledge-connect is focused, and the summary matches what you get after install.
- ★★★★★Sophia Tandon· Nov 19, 2024
yuque-personal-knowledge-connect reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 71