Update to DeepL

{
  "name": "translation-rules",
  "description": "The standard rules for translating, editing glossaries, rephrasing and proofreading with DeepL —\napply on every DeepL job. Use when the user asks to translate, localize, rephrase or proofread\nanything, when they say \"apply our translation rules\" / \"translate with our rules\", or before any\nglossary, style-rule or formality change.\n",
  "included_files": [],
  "skill_md_contents": "---\nname: translation-rules\ndescription: |\n  The standard rules for translating, editing glossaries, rephrasing and proofreading with DeepL —\n  apply on every DeepL job. Use when the user asks to translate, localize, rephrase or proofread\n  anything, when they say \"apply our translation rules\" / \"translate with our rules\", or before any\n  glossary, style-rule or formality change.\nlicense: MIT\nmetadata:\n  author: DeepL\n  version: \"3.0\"\n---\n\n# DeepL translation rules (v3)\n\n## What this skill does\n\nDefines how every DeepL job is run: what always goes through DeepL tools, what must be preserved,\nwhen to ask the user, and how glossaries, style rules and formality are chosen. When this skill is\nactive, follow every rule below on each job.\n\n## Universal rules (every translation)\n\n1. **Never translate URLs.** Localized URLs break links. You may *ask* whether paths should be\n   localized (`/en/industries/` → `/de/industries/`), but never localize by default.\n2. **Always translate through DeepL tools**, never from your own knowledge: `translate-text` for\n   text, `upload-document` → `get-document-status` → `download-document` for files.\n3. **Preserve exactly as in the source:** numbers, units, product names, placeholders and tags.\n4. **Check glossary coverage before translating.** If a glossary exists for the domain but not for\n   this language pair (EN-DE exists, the user wants RU), say so instead of silently translating\n   without it.\n5. **Don't re-ask for settings that are already set or known.** Apply the formality and style rules\n   in force. Only when formality is unknown do you decide — infer it from prior translations, or ask\n   (see *Style rules and formality*).\n6. **Ask clarifying questions only when errors are expensive** — large batch jobs, regulated\n   content. For small translations, just translate.\n\n## Translate text (`translate-text`, `get-source-languages`, `get-target-languages`)\n\n- **Auto-detect the source language** (leave source unset), except when a glossary is applied —\n  glossaries require an explicit source language.\n- **Ask when the target language is ambiguous** (\"translate this\"). For English targets use EN-US\n  unless the context clearly calls for EN-GB.\n- **Never invent support.** Check `get-source-languages` / `get-target-languages` when unsure and\n  offer the closest supported option instead of translating from your own knowledge.\n- **Pass the content domain as `context`** (\"legal contract\", \"marketing copy\"). It improves quality\n  and is not itself translated.\n- **Ad-hoc steering goes into `customInstructions`** (\"keep it punchy\") — max 10, each under 300\n  characters.\n\n## Translate documents (`upload-document` → `get-document-status` → `download-document`)\n\n- **Supported formats:** docx, pptx, xlsx, pdf, html, txt, srt, xliff.\n- **Layout is preserved by DeepL.** Never reconstruct the document yourself.\n\n## Glossaries (`list-glossaries`, `get-glossary-info`, `get-glossary-dictionary-entries`)\n\n- **Auto-select the glossary from the translation context** when the match is clear from its name;\n  otherwise ask the user which one to apply.\n- **Always tell the user the name of the glossary you used.**\n\n## Editing customizations (create and edit glossaries)\n\n- **Show a diff before any glossary change** — entries added, changed and removed — and get explicit\n  confirmation before writing.\n- **Extend before creating.** Default to adding entries to the existing glossary for that domain.\n  Create a new glossary only when the domain or audience is genuinely different.\n- **Source terms from real content only.** When asked to build or extend a glossary from a document\n  or past translations, propose candidate pairs extracted from that content and let the user approve\n  them. Never invent terminology.\n\n## Style rules and formality (`list-style-rule-sets`, `get-style-rule-set`, `get-custom-instruction`)\n\n- **Apply what is already set** without asking (rule 5 above).\n- **When formality is not set or not inferable, confirm the setting with the user** before applying\n  it.\n\n## Rephrase and tone (`rephrase-text`)\n\n- **Styles:** academic, business, casual, simple. **Tones:** confident, diplomatic, enthusiastic,\n  friendly. One or the other, never both.\n- **Keep the original language.** Rephrasing is not translation.\n\n## Proofread (`correct-text`)\n\n- **Fix typos, grammar and punctuation only.** Keep the author's wording and voice.\n"
}