Yuque Personal Knowledge Connect
Wire your personal Yuque docs into a connected knowledge graph with search, cross-links, and optional knowledge-map pages via yuque-mcp.
Overview
Yuque Personal Knowledge Connect is an agent skill most often used in Build (also Idea/research, Grow/content) that discovers related Yuque documents and builds bidirectional links and knowledge maps through yuque-mcp.
Install
npx skills add https://github.com/yuque/yuque-plugin --skill yuque-personal-knowledge-connectWhat is this skill?
- Six-step workflow: anchor doc or topic → search → read → map links → update docs → optional knowledge-map page
- Uses yuque_search, yuque_get_doc, yuque_list_repos, yuque_list_docs, yuque_update_doc, yuque_create_doc
- Personal/individual scope only—operates on your own Yuque repos with your token
- Supports Chinese and English trigger phrases for finding related documents
- Apache-2.0 licensed Yuque plugin skill paired with yuque-mcp server
- Six yuque-mcp tools in the documented workflow
- Skill metadata version 1.0
Adoption & trust: 516 installs on skills.sh; 73 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your Yuque workspace has grown into siloed pages and you cannot see how ideas, specs, and runbooks relate to a topic.
Who is it for?
Indie builders who already document in Yuque, run Claude Code or Cursor with MCP, and want agent-assisted linking without manually opening every repo.
Skip if: Team-wide Yuque governance, non-Yuque wikis, or environments where yuque-mcp and a personal Yuque token are not available.
When should I use this skill?
User wants related Yuque documents, knowledge links, or a knowledge map—e.g. "有哪些相关文档", "find related docs", "帮我建立知识关联", "构建知识图谱".
What do I get? / Deliverables
You get a mapped set of related documents, suggested or applied cross-links, and optionally a new knowledge-map doc that ties the topic together in Yuque.
- Relationship map of related Yuque documents for a topic or seed doc
- Updated documents with cross-reference links where appropriate
- Optional new knowledge-map document in Yuque
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Personal knowledge bases are maintained while building and shipping; canonical shelf is Build/docs because the skill mutates and structures documentation assets. Docs subphase fits repo scanning, bidirectional links, and knowledge-map creation inside Yuque rather than application code.
Where it fits
Search Yuque for prior notes on a market or competitor theme before committing to a build.
Link API design doc, ADR, and runbook pages for one feature so the agent can traverse them.
Surface scattered scope notes into one knowledge-map doc for a prototype decision.
Reconnect incident postmortems and config docs after an outage so future fixes start from linked context.
How it compares
Use as a Yuque-specific doc graph skill, not a general RAG pipeline or standalone MCP server—the server is a prerequisite, not included in the skill package alone.
Common Questions / FAQ
Who is yuque-personal-knowledge-connect for?
Individual developers and solo founders who store personal notes and specs in Yuque and use an MCP-capable agent to explore and link their own documentation.
When should I use yuque-personal-knowledge-connect?
During Idea/research when consolidating topic background; in Build/docs when linking specs before implementation; in Grow/content when curating published or internal playbooks—whenever you ask for related docs or a knowledge graph in Yuque.
Is yuque-personal-knowledge-connect safe to install?
It can read and update your Yuque docs via MCP—use a personal token with least privilege and review the Security Audits panel on this Prism page before connecting production knowledge bases.
SKILL.md
READMESKILL.md - Yuque Personal Knowledge Connect
# 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 keyword - `yuque_get_doc` — Read document content to analyze connections - `yuque_list_repos` — List personal repos to scan - `yuque_list_docs` — List documents in repos for broader discovery - `yuque_update_doc` — Add cross-reference links to documents - `yuque_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: ```markdown # 🗺️ 知识关联图：[主题/文档标题] > 基于「[起始文档]」发现的知识网络 > 扫描范围：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: - "要在这些文档中添加相互引用链接吗？" ### S