Update to SQL Copilot

{
  "description": "Translate SQL between named database platforms while preserving semantics.",
  "included_files": [],
  "name": "translate-sql-dialect",
  "skill_md_contents": "---\nname: translate-sql-dialect\ndescription: Translate SQL between named database platforms while preserving semantics.\n---\n\n# Translate Sql Dialect\n\n**Trigger:** Translate SQL between named database platforms while preserving semantics.\n\n## Workflow\n1. Identify source and target engine, version when consequential, and any source functions or UDFs.\n2. Translate syntax and behavior: quoting, LIMIT/TOP/FETCH, date/time, null-safe equality, upserts, JSON, arrays, QUALIFY, transactions and stored procedure constructs.\n3. Call out features without direct equivalents rather than inventing functions.\n4. Mark where silent behavior changes may arise: Oracle empty strings, string collation, timestamp zones, integer division, regex or casting.\n5. Supply a comparison validation plan: sample inputs, cardinalities, boundary rows and totals.\n\n## Critical standard\nNo mixed-dialect SQL; confirm version-sensitive syntax from official platform documentation.\n\n## Evidence and execution\nOnly say \"executed\", \"passed\", \"observed\", \"optimized\" or \"deployed\" when a connected tool returned evidence for that claim. An SQL draft, a textual review, or local fixture proof alone is not production validation. Never ask the user to paste passwords or raw confidential records.\n\n## Supporting references\n- Read `../../references/dialects.md` when relevant.\n- Read `../../references/official-docs.md` when relevant.\n- Read `../../references/null-time-types.md` when relevant.\n\n## Return\nTarget-dialect SQL, differences that matter, and equivalence checks.\n"
}