diff --git a/.agents/skills/docs-en-improvement/SKILL.md b/.agents/skills/docs-en-improvement/SKILL.md
new file mode 100644
index 0000000000..5be1fb6d84
--- /dev/null
+++ b/.agents/skills/docs-en-improvement/SKILL.md
@@ -0,0 +1,24 @@
+---
+name: docs-en-improvement
+description: Improve English documentation under `website/docs/en` by rewriting unnatural translated sentences into clear, professional English while preserving meaning. Use when editing or polishing English docs.
+---
+
+# Docs En Improvement
+
+## Steps
+
+1. Focus on files in `website/docs/en`.
+
+2. Rewrite only sentences that clearly improve clarity, correctness, or naturalness in English.
+
+3. Preserve original meaning exactly; do not introduce new claims or remove technical details.
+
+4. If a file in `website/docs/en` is updated, check the mirrored file in `website/docs/zh` and apply equivalent updates when needed.
+
+## Constraints
+
+- Limit each PR to 10 documentation files or fewer.
+- Start PR titles with `docs:`.
+- Keep reasonable technical abbreviations (for example, `dev server`).
+- Keep wording simple and readable for non-native English readers.
+- Use sentence case for Markdown headings.
diff --git a/.github/docs-en-improvement.prompt.yml b/.github/docs-en-improvement.prompt.yml
deleted file mode 100644
index 5605a98b28..0000000000
--- a/.github/docs-en-improvement.prompt.yml
+++ /dev/null
@@ -1,30 +0,0 @@
-messages:
-  - role: system
-    content: >-
-      Improve the English docs in `website/docs/en`. Many paragraphs were
-      translated from Chinese and may sound unnatural.
-
-
-      Rewrite sentences that don't read like authentic, professional English —
-      **without changing their meaning** — so they match the tone of
-      high-quality open-source docs.
-
-
-      - **IMPORTANT:** Only change a sentence if it clearly improves clarity or
-      correctness.
-
-      - **IMPORTANT:** Don't alter the original meaning.
-
-      - If you edit files in `docs/en`, check the same files in `docs/zh` to see
-      if similar updates are needed.
-
-      - Use clear, simple language for non-native English readers.
-
-      - Keep reasonable technical abbreviations (e.g., `dev server`).
-
-      - Use sentence case for Markdown headings.
-
-      - Don't change more than 10 files in one PR.
-
-      - Start PR titles with `docs:`.
-model: openai/gpt-5