yuque-lakebook-export
Skill18 starsChanged 8 days agoMITView on GitHub
Use when exporting Yuque or .lakebook content to local Markdown for Obsidian migration or cleanup.
In this repository55 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ax-extract-workflowSkill
- conversation-json-to-mdSkill
- feature-doc-splitterSkill
- frontend-quality-guardrailsSkill
- git-commit-onlySkill
- git-pushing-fastSkill
- git-push-secondary-merge-primarySkill
- git-stepwise-commitSkill
- git-weekly-reportSkill
- linkedinSkill
- logo-design-boardSkill
- mac-software-storage-cleanupSkill
- multi-lang-readmeSkill
- novel-writerSkill
- react-component-hook-guidelinesSkill
- routerbase-api-integrationSkill
- routerbase-media-generationSkill
- routerbase-model-routingSkill
- topic-bookmarks-reorganizerSkill
- tree-ring-memorySkill
- tweetclaw-twitter-automationSkill
- ui-layout-analyzerSkill
- wechat-theme-extractorSkill
- weixin-article-to-obsidianSkill
- xquik-dataSkill
- x-twitter-scraperSkill
- ax-extract-workflow-cnSkill
- conversation-json-to-md-cnSkill
- feature-doc-splitter-cnSkill
- frontend-quality-guardrails-cnSkill
- git-commit-only-cnSkill
- git-pushing-fast-cnSkill
- git-push-secondary-merge-primary-cnSkill
- git-stepwise-commit-cnSkill
- git-weekly-report-cnSkill
- linkedin-cnSkill
- logo-design-board-cnSkill
- mac-software-storage-cleanup-cnSkill
- multi-lang-readme-cnSkill
- novel-writer-cnSkill
- react-component-hook-guidelines-cnSkill
- routerbase-api-integration-cnSkill
- routerbase-media-generation-cnSkill
- routerbase-model-routing-cnSkill
- topic-bookmarks-reorganizer-cnSkill
- tree-ring-memory-cnSkill
- tweetclaw-twitter-automation-cnSkill
- ui-layout-analyzer-cnSkill
- wechat-theme-extractor-cnSkill
- weixin-article-to-obsidian-cnSkill
- xquik-data-cnSkill
- x-twitter-scraper-cnSkill
- yuque-lakebook-export-cnSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 6 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Use this skill when the user asks for:
- Distinctive: line 24
Do not use this skill for:
- Distinctive: line 32
Prefer non-interactive execution so the agent can run deterministically.
- Distinctive: line 33
Before any non-interactive export, the agent must confirm the output root directory with the user.
- Distinctive: line 34
If the user has not provided an output directory, ask a concise question and wait for the user's answer before running the export command.
- Very specific: line 35
Prefer uv consistently. Do not create temporary .venv or similar task-local environments in the working directory.
- Very specific: line 36
Before running any uv command, first check whether uv is available in the environment.
- Very specific: line 37
If uv is not installed or not available in PATH, the agent must ask the user for confirmation before installing uv.
- Distinctive: line 39
Use this entrypoint for agent execution:
- Very specific: line 72
Do not manually create temporary virtual environments in the current working directory, the user's download directory, or any task …
- Very specific: line 81
If export fails, inspect the batch log written next to the input .lakebook files.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Yuque Lakebook Export
Overview
Convert Yuque knowledge bases, Yuque documents, or .lakebook files into local Markdown folders prepared for Obsidian. The workflow supports single or batch exports and cleanup for common migration issues such as missing images, cropped image mismatches, broken internal links, wrong folder hierarchy, and Markdown table rendering problems.
When to Use
Use this skill when the user asks for:
- Exporting one or more Yuque
.lakebookfiles - Converting a Yuque knowledge base into Markdown
- Migrating Yuque content into Obsidian
- Fixing Yuque export issues around images, cropped images, internal links, hierarchy, or tables
Do not use
Do not use this skill for:
- Generic Markdown editing that does not involve Yuque or
.lakebook - Website scraping tasks
- Export tasks that already come from a non-Yuque format
Instructions
- Prefer non-interactive execution so the agent can run deterministically.
- Before any non-interactive export, the agent must confirm the output root directory with the user. Do not choose an output directory on the user's behalf.
- If the user has not provided an output directory, ask a concise question and wait for the user's answer before running the export command.
- Prefer
uvconsistently. Do not create temporary.venvor similar task-local environments in the working directory. - Before running any
uvcommand, first check whetheruvis available in the environment. - If
uvis not installed or not available inPATH, the agent must ask the user for confirmation before installinguv. Do not install it silently. - Before running
uv syncoruv run python scripts/cli.py ..., the agent must first switch into the installed skill tool directory, meaning the directory that contains thisSKILL.md,pyproject.toml,uv.lock, andscripts/. Do not run these commands directly from the.lakebooksource directory, the output directory, or the user's current workspace root. - Use this entrypoint for agent execution:
uv run python scripts/cli.py- Sync dependencies before first use:
uv sync- Recommended command order:
cd /path/to/installed-skill-root
uv sync
uv run python scripts/cli.py ...- Standard single-file execution:
uv run python scripts/cli.py -l "/path/to/your_file.lakebook" -o "/target/root"- Standard batch execution:
uv run python scripts/cli.py -l "/path/to/your_file_1.lakebook" "/path/to/your_file_2.lakebook" -o "/target/root"- Although
scripts/cli.pystill supports interactive terminal selection for manual human use, agents must not rely on interactive mode because they cannot reliably capture terminal interaction state. Always pass explicit-land-oarguments. - Do not manually create temporary virtual environments in the current working directory, the user's download directory, or any task directory; dependencies should be managed by
uvfrom the skill tool directory. - Some Yuque exports include
<!doctype lake>at the start of the document body; older implementations could render this as a straylake##prefix in Markdown. The current skill implementation already handles this case. - After export, verify:
.mdfiles exist- sibling
.assetsfolders exist - internal links are relative Markdown paths
- images render in Obsidian
- exported documents do not start with an erroneous
lake##prefix
- If export fails, inspect the batch log written next to the input
.lakebookfiles.
For detailed behavior, troubleshooting, and output rules, read references/usage.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

