docs(meta): translate SKILL.md into English per guidelines

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

skills/skill-update/SKILL.md

@@ -3,15 +3,15 @@ name: skill-update
 description: Update an existing skill in the jsc skill set. List all skills, let the user pick one, ask update details via decision tree, apply the change, re-check against the guidelines checklist until it passes, then open a PR via jsc-git pr. Use for modifying a skill; not for creating (skill-new) or removing (skill-delete).
 ---
 
-# skill-update — 更新技能
+# skill-update — update a skill
 
-準則單一來源：[`../../references/guidelines.md`](../../references/guidelines.md)。
+Single source of guidelines: [`../../references/guidelines.md`](../../references/guidelines.md).
 
-## 流程
+## Flow
 
-1. 列出技能組內含的所有技能：掃描 `jsc-*/skills/*/SKILL.md`，以「domain / 名稱 / description」清單呈現。
-2. 讓使用者選擇要更新的技能。
-3. 依 `jsc-ask:ask` 決策樹詢問更新細節（改目標？改觸發時機？改流程？下放 hook 或工具？），每個選項標明影響範圍（例：改名會使既有呼叫指令失效）。
-4. 更新技能（此步驟**必須以 sub agent 執行**）：修改 SKILL.md 與關聯檔案，同步 domain README「Skills 目錄」與三份 manifest 的 version bump。
-5. 依 guidelines.md「審核檢查清單」逐項檢查；**不符合就回到步驟 3** 重新詢問並修正，直到全部通過。
-6. 呼叫 `jsc-git:pr` 建立 Push Request。
+1. List every skill in the skill set: scan `jsc-*/skills/*/SKILL.md` and present a "domain / name / description" list.
+2. Let the user pick the skill to update.
+3. Ask for update details via the `jsc-ask:ask` decision tree (change the goal? the trigger? the flow? move rules down to a hook or a tool?). Every option states its impact scope (example: renaming breaks the existing invocation command).
+4. Update the skill — this step MUST run as a sub agent: modify SKILL.md and related files, sync the domain README's 「Skills 目錄」 section, and bump the version in all three manifests.
+5. Check every item of the guidelines.md audit checklist. On any failure, **return to step 3**: ask again and fix, until all items pass.
+6. Call `jsc-git:pr` to open a Push Request.