Baoyu URL To Markdown
sdyckjq-lab/llm-wiki-skill
Fetch any URL and convert to markdown using Chrome CDP. An agent skill from sdyckjq-lab/llm-wiki-skill.
Polish rough Yuque notes into structured, readable documents while preserving their meaning.
Install Note Refine
$ npx skills add yuque/yuque-ecosystem --skill note-refine -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install yuque/yuque-ecosystem note-refine --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/yuque/yuque-ecosystem.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/note-refine .claude/skills/note-refine && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "note-refine" agent skill from https://github.com/yuque/yuque-ecosystem/tree/main/skills/note-refine into .claude/skills/note-refine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "note-refine", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/yuque/yuque-ecosystem/tree/main/skills/note-refineType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add yuque/yuque-ecosystem --skill note-refine -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install yuque/yuque-ecosystem note-refine --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yuque/yuque-ecosystem.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/note-refine .agents/skills/note-refine && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "note-refine" agent skill from https://github.com/yuque/yuque-ecosystem/tree/main/skills/note-refine into .agents/skills/note-refine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "note-refine", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add yuque/yuque-ecosystem --skill note-refine -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install yuque/yuque-ecosystem note-refine --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yuque/yuque-ecosystem.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/note-refine .cursor/skills/note-refine && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "note-refine" agent skill from https://github.com/yuque/yuque-ecosystem/tree/main/skills/note-refine into .cursor/skills/note-refine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "note-refine", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/yuque/yuque-ecosystem.git --path skills/note-refine--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add yuque/yuque-ecosystem --skill note-refine -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install yuque/yuque-ecosystem note-refine --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yuque/yuque-ecosystem.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/note-refine .gemini/skills/note-refine && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "note-refine" agent skill from https://github.com/yuque/yuque-ecosystem/tree/main/skills/note-refine into .gemini/skills/note-refine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "note-refine", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install yuque/yuque-ecosystem note-refineInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add yuque/yuque-ecosystem --skill note-refine -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/yuque/yuque-ecosystem.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/note-refine .github/skills/note-refine && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "note-refine" agent skill from https://github.com/yuque/yuque-ecosystem/tree/main/skills/note-refine into .github/skills/note-refine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "note-refine", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add yuque/yuque-ecosystem --skill note-refine -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install yuque/yuque-ecosystem note-refine --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yuque/yuque-ecosystem.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/note-refine .opencode/skills/note-refine && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "note-refine" agent skill from https://github.com/yuque/yuque-ecosystem/tree/main/skills/note-refine into .opencode/skills/note-refine/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "note-refine", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
note-refine- GitHub stars
- 228
- Token cost
- ~1.5k tokens
- SKILL.md length
- 711 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- MIT
At a glance
Polish rough Yuque notes into structured, readable documents while preserving their meaning.
- Works in 5 steps: Get the Source Notes → Analyze the Current State → Refine the Content → …
- The user wants to clean up a draft
- SKILL.md covers When to Use, Required MCP Tools, Workflow and Guidelines, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Note Refine is an agent skill from yuque/yuque-ecosystem. Polish rough Yuque notes into structured, readable documents while preserving their meaning. Use when the user wants to clean up a draft, improve layout, or turn fragments into a document; trigger phrases include “帮我整理一下这篇笔记”, “把这个文档排版优化一下”, and “polish my notes”.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires the yuque-mcp MCP server connected with a personal Yuque token
It sits in Knowledge Management. The repository describes itself as: Yuque AI Ecosystem — MCP Server, Skills & Plugin for Yuque (语雀). The licence is MIT.
When your agent uses it
- The user wants to clean up a draft
- Turn fragments into a document
- Trigger phrases include 帮我整理一下这篇笔记
- Polish my notes
Example prompts
- “帮我整理一下这篇笔记”
- “把这个文档排版优化一下”
- “polish my notes”
- “/note-refine”
Requirements
- Compatibility (from SKILL.md): Requires the yuque-mcp MCP server connected with a personal Yuque token
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 2959228. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires the yuque-mcp MCP server connected with a personal Yuque token
From compatibility in the SKILL.md frontmatter.
Context cost
Note Refine loads about 1.5k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 711 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from yuque/yuque-ecosystem at commit 2959228, republished under its MIT licence (© yuque). 711 words, ~1,506 tokens.
Download SKILL.mdSave it as
.claude/skills/note-refine/SKILL.md (or your agent's skills folder).- name
- note-refine
- description
- Polish rough Yuque notes into structured, readable documents while preserving their meaning. Use when the user wants to clean up a draft, improve layout, or turn fragments into a document; trigger phrases include “帮我整理一下这篇笔记”, “把这个文档排版优化一下”, and “polish my notes”.
- compatibility
- Requires the yuque-mcp MCP server connected with a personal Yuque token
- license
- MIT
- metadata.author
- yuque
- metadata.version
- 1.0
Note Refine — Polish Rough Notes into Quality Documents
Transform rough, unstructured notes into well-organized, readable documents. Adds proper headings, table of contents, improves expression, and enhances formatting — all while preserving the original meaning.
When to Use
- User has a rough draft or messy notes they want to clean up
- User says "帮我整理一下这篇笔记", "polish my notes", "把这个文档排版优化一下"
- User wants to improve readability of an existing Yuque document
- User has bullet points or fragments they want turned into a proper document
Required MCP Tools
All tools are from the yuque-mcp server:
yuque_get_doc— Read the original document contentyuque_update_doc— Update the document with refined content
Workflow
Step 1: Get the Source Notes
Case A — Yuque document link:
Extract repo_id and doc_id from the URL and fetch the content:
Tool: yuque_get_doc
Parameters:
repo_id: "<namespace>"
doc_id: "<slug>"Case B — User pastes text directly: Use the provided text as the source content. No tool call needed.
If the document is not found (404) or permission denied (403), inform the user and stop.
Step 2: Analyze the Current State
Before refining, assess the notes on these dimensions:
| Dimension | What to Check |
|---|---|
| Structure | Are there headings? Is there a logical flow? |
| Completeness | Are sentences complete? Are there dangling thoughts? |
| Formatting | Consistent use of lists, code blocks, emphasis? |
| Readability | Paragraph length, sentence clarity, jargon usage? |
| Organization | Is related content grouped together? |
Mentally categorize the refinement level needed:
- Light polish — Good structure, just needs formatting and minor wording fixes
- Medium refine — Has content but needs reorganization and better headings
- Heavy restructure — Fragments and bullet points that need to become a proper document
Step 3: Refine the Content
Apply the following improvements while strictly preserving the original meaning:
Structure improvements:
- Add a clear title if missing
- Add hierarchical headings (H2, H3) to break content into logical sections
- Reorder content so related ideas are grouped together
- Add a brief introduction paragraph if the document jumps straight into details
Expression improvements:
- Complete sentence fragments into full sentences
- Fix grammatical errors and typos
- Replace vague language with precise terms
- Smooth transitions between sections
- Keep the author's voice and tone — don't make casual notes sound like academic papers
Formatting improvements:
- Use bullet lists for parallel items
- Use numbered lists for sequential steps
- Use code blocks for code, commands, or technical content
- Use tables for structured comparisons
- Use bold for key terms on first mention
- Use blockquotes for important callouts
- Ensure consistent formatting throughout
What NOT to change:
- Do not add new information or opinions not present in the original
- Do not remove content the author wrote (unless it's clearly a duplicate)
- Do not change technical terms or proper nouns
- Do not alter the author's conclusions or viewpoints
- Do not over-formalize casual notes if the user didn't ask for it
Show full SKILL.md (265 more words)Show less
Step 4: Present the Refined Version
Show the user a comparison summary and the refined document:
## ✨ 笔记优化完成
### 优化概览
| 项目 | 优化前 | 优化后 |
|------|--------|--------|
| 结构 | [e.g., 无标题，纯文本] | [e.g., 3 个章节，层级清晰] |
| 段落数 | X | Y |
| 字数 | ~X 字 | ~Y 字 |
### 主要改动
1. [改动 1：e.g., 添加了三级标题结构]
2. [改动 2：e.g., 将零散要点整合为完整段落]
3. [改动 3：e.g., 统一了列表格式]
---
[完整的优化后文档内容]Step 5: Save Changes (Optional)
Ask the user: "要把优化后的内容更新到原文档吗？"
If the user confirms and the source was a Yuque document:
Tool: yuque_update_doc
Parameters:
repo_id: "<namespace>"
doc_id: "<slug>"
body: "<refined content in markdown>"After saving, confirm: "文档已更新：[文档链接]"
If the user wants to keep the original and save as a new version: Inform the user: "语雀会自动保留历史版本，更新后你仍然可以在版本历史中查看原始内容。"
If the source was pasted text:
Just present the refined version in chat. If the user wants to save it, ask which knowledge base and use yuque_create_doc.
Guidelines
- Always answer in the same language as the original notes (Chinese or English)
- The golden rule: preserve meaning, improve form
- Show the user what you changed and why — transparency builds trust
- For light polish, don't over-engineer — sometimes notes just need minor fixes
- For heavy restructure, confirm the proposed structure with the user before saving
- If the notes contain TODO items or unfinished thoughts, preserve them as-is (mark with
<!-- TODO -->if needed) - Respect the author's writing style — don't turn informal notes into formal reports unless asked
Error Handling
| Situation | Action |
|---|---|
| Document not found (404) | Inform user the document may have been deleted or the link is incorrect |
| Permission denied (403) | Tell user they may lack permission to access or edit this document |
| Document content is empty | Inform user: "该文档内容为空，没有可优化的内容" |
yuque_update_doc fails | Present the refined content in chat and suggest the user copy-paste it manually |
| Content is already well-structured | Tell the user: "这篇文档结构已经很清晰了，只做了少量微调" — don't force unnecessary changes |
| Content is too short (< 50 chars) | Inform user the content is too brief to meaningfully refine, ask if they want to expand it instead |
© yuque, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/note-refine of yuque/yuque-ecosystem.
Open the folder on GitHubat commit 2959228
Compare with similar skills
Note Refine next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Note Refine this skillyuque/yuque-ecosystem | 228 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Baoyu URL To Markdownsdyckjq-lab/llm-wiki-skill | 2.5k | 3 repos | ~3.2k | Automated safety check: Pass | None | |
| Logseq Review Workflow Evallogseq/logseq | 45k | — | ~1k | Automated safety check: Pass | AGPL-3.0 | |
| Obsidian CLIAtmosphere/atmosphere | 3.8k | 13 repos | ~795 | Automated safety check: Pass | Apache-2.0 | |
| Esm Cjs Risk Scanlogseq/logseq | 45k | — | ~3.3k | Automated safety check: Pass | AGPL-3.0 | |
| Capture Conversationoutline/outline | 41k | — | ~474 | Automated safety check: Pass | Custom licence |
Similar skills
Logseq Review Workflow Eval
logseq/logseq
Compare two revisions of the Logseq logseq-review-workflow skill by running the same review prompt against isolated before and after skill snapshots, collecting both outputs, and producing a…
Obsidian CLI
Atmosphere/atmosphere
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more.
Esm Cjs Risk Scan
logseq/logseq
Scan Logseq ClojureScript Node/Electron targets for npm module loading risks, especially ESM-only packages that may fail when loaded through js/require or shadow-cljs require-based shims.
Capture Conversation
outline/outline
Save the current conversation, a decision, or a set of notes as a document in an Outline collection; use when the user wants to keep what was discussed in their knowledge base.
Karpathy LLM Wiki
Astro-Han/karpathy-llm-wiki
A skill your agent uses when building or maintaining a personal LLM-powered knowledge base.
More from yuque/yuque-ecosystem
All 8 skills in this repoDaily Capture
yuque/yuque-ecosystem
Capture fleeting ideas in Yuque and periodically organize them into structured thematic notes.
Knowledge Connect
yuque/yuque-ecosystem
Analyze Yuque documents to uncover related topics, complementary notes, and cross-reference opportunities.
Reading Digest
yuque/yuque-ecosystem
Extract core insights, golden quotes, and action items from articles, then create structured Yuque reading notes.
Smart Search
yuque/yuque-ecosystem
Search personal Yuque knowledge bases with natural-language queries and synthesize answers with source links.
Smart Summary
yuque/yuque-ecosystem
Summarize a Yuque document or knowledge base at one-line, key-point, or detailed granularity.
Stale Detector
yuque/yuque-ecosystem
Scan a Yuque knowledge base for stale or outdated documents and recommend updates or archiving.
Related
Categories
Questions about Note Refine
What does Note Refine do?
Polish rough Yuque notes into structured, readable documents while preserving their meaning. Note Refine is an agent skill from yuque/yuque-ecosystem. Polish rough Yuque notes into structured, readable documents while preserving their meaning.
When should I use Note Refine?
Note Refine fits situations like: the user wants to clean up a draft; turn fragments into a document; trigger phrases include 帮我整理一下这篇笔记; polish my notes.
How do I install Note Refine in Claude Code?
Run `npx skills add yuque/yuque-ecosystem --skill note-refine -a claude-code`. Or copy the skill folder (skills/note-refine in yuque/yuque-ecosystem) into .claude/skills/note-refine in your project. Claude Code loads it when a task matches its description.
How do I install Note Refine in Codex?
Run `npx skills add yuque/yuque-ecosystem --skill note-refine -a codex`. Or copy the skill folder (skills/note-refine in yuque/yuque-ecosystem) into .agents/skills/note-refine in your project. Codex loads it when a task matches its description.
Can I use Note Refine in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yuque/yuque-ecosystem --skill note-refine -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/note-refine, .gemini/skills/note-refine, .github/skills/note-refine and .opencode/skills/note-refine in your project.
What does Note Refine need to run?
SKILL.md names no scripts, command-line tools or credentials: Note Refine is instructions for the agent only. Compatibility (from SKILL.md): Requires the yuque-mcp MCP server connected with a personal Yuque token.
Does Note Refine access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Note Refine safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Note Refine use?
Note Refine is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Note Refine use?
About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Note Refine?
Skills that share tags, products or a category with Note Refine: Baoyu URL To Markdown (sdyckjq-lab/llm-wiki-skill, 2.5k stars), Logseq Review Workflow Eval (logseq/logseq, 45k stars), Obsidian CLI (Atmosphere/atmosphere, 3.8k stars) and Esm Cjs Risk Scan (logseq/logseq, 45k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Note Refine?
yuque (a GitHub organization) maintains it in yuque/yuque-ecosystem, which has 228 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on July 15, 2026.
Source: yuque/yuque-ecosystem on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.