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

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

skills/skill-delete/SKILL.md

@@ -3,20 +3,20 @@ name: skill-delete
 description: Remove a skill from the jsc skill set safely. List skills, let the user pick, inventory every file referencing the skill via a sub agent, fix each affected file through decision-tree questions until guideline checks pass, then delete the skill and open a PR via jsc-git pr. Use only for removal; not for renaming (use skill-update).
 ---
 
-# skill-delete — 刪除技能
+# skill-delete — delete a skill
 
-準則單一來源：[`../../references/guidelines.md`](../../references/guidelines.md)。
+Single source of guidelines: [`../../references/guidelines.md`](../../references/guidelines.md).
 
-## 流程
+## Flow
 
-1. 列出技能組內含的所有技能：掃描 `jsc-*/skills/*/SKILL.md`。
-2. 讓使用者選擇要刪除的技能（選項標明影響範圍：被哪些技能引用、刪除後指令即失效）。
-3. 盤點與此技能關聯的所有檔案，此步驟**必須以 sub agent 執行**：
-   - `grep -r` 技能名稱與 `/jsc-{domain}:{name}`，掃過所有 jsc-* 存取庫
-   - 其他 SKILL.md 的引用、domain README「Skills 目錄」、`plugins/jsc` 的兩份 marketplace.json、`tools/`、`jsc-hooks` 接線
-4. 逐檔執行：
-   1. 判斷刪除技能後，該檔是否需要修正才能維持既有功能；**不需要修正就跳過**剩下的流程。
-   2. 依 `jsc-ask:ask` 決策樹詢問修正細節（改為呼叫替代技能？內聯流程？一併移除功能？），每個選項標明影響範圍。
-   3. 修正後依 guidelines.md「審核檢查清單」檢查；不符合就回到步驟 4.2。
-5. 刪除技能目錄 `skills/{name}/`，同步 domain README 與三份 manifest 的 version bump。
-6. 呼叫 `jsc-git:pr` 建立 Push Request。
+1. List every skill in the skill set: scan `jsc-*/skills/*/SKILL.md`.
+2. Let the user pick the skill to delete. Options state the impact scope: which skills reference it, and that its command stops working after deletion.
+3. Inventory every file related to the skill — this step MUST run as a sub agent:
+   - `grep -r` for the skill name and `/jsc-{domain}:{name}` across all jsc-* repositories
+   - References in other SKILL.md files, the domain README's 「Skills 目錄」 section, the two marketplace.json files in `plugins/jsc`, `tools/`, and the `jsc-hooks` wiring
+4. For each affected file:
+   1. Decide whether the file needs a fix to keep its current behavior after the deletion. If no fix is needed, **skip the rest of this loop**.
+   2. Ask for fix details via the `jsc-ask:ask` decision tree (call a replacement skill? inline the flow? drop the feature too?). Every option states its impact scope.
+   3. After fixing, check the guidelines.md audit checklist. On failure, return to step 4.2.
+5. Delete the skill directory `skills/{name}/`, then sync the domain README and bump the version in all three manifests.
+6. Call `jsc-git:pr` to open a Push Request.