Yuque Connector

Problem It Solves

Local office files and Yuque knowledge bases often need a repeatable sync path: Markdown, Word, Excel, CSV, JSON, and similar files may need to be imported into Yuque, while documents, directories, notes, or whole repositories need to be downloaded as local .md files for editing, backup, and search. Manual copy-paste can lose formatting, scatter content, and make rate-limit failures hard to recover from.

How The Skill Works

The skill uses Yuque MCP to provide read/write operations across import, download, organization, and update workflows:

• Local file import: .md and .html can be imported directly; .docx, .xlsx, .csv, .txt, and .json are read and converted to Markdown; zip files or folders can create documents in batch.
• Yuque content download: supports single documents, selected directories, whole knowledge bases, and notes, saving them as local .md files with filenames derived from the document title.
• Knowledge-base management: handles TOC structure, document search, document updates, notes, and board resource creation where supported.
• Stability handling: batch downloads use spacing, and requests retry under 429, 500, or network timeout conditions, then report failure details.

Boundaries And Cautions

• Image upload is constrained by MCP; external image URLs can be referenced in Markdown, while general attachments may need Yuque-native handling.
• Binary media such as video or audio is usually easier to upload through the Yuque web interface.
• A valid Yuque Token and a working MCP service are required; local configuration may need to be rewritten after moving environments.
• Batch operations should respect directory selection and rate-limit signals to avoid excessive requests.