Update to Unix Copilot

{
  "description": "Plan and troubleshoot SSH, SCP, rsync and remote shell workflows with safe quoting, authentication and host verification.",
  "included_files": [],
  "name": "ssh-remote-ops",
  "skill_md_contents": "---\nname: ssh-remote-ops\ndescription: Plan and troubleshoot SSH, SCP, rsync and remote shell workflows with safe quoting, authentication and host verification.\n---\n\n# Remote Unix operations\n\n## Scope and execution truth\nThis is a skills-only assistant workflow. Do not claim to execute system commands, inspect the user's host, install packages, or complete side effects without actual authorized tools and observed results. User-pasted output is evidence, not a machine connection.\n\n## Procedure\n1. Distinguish local shell expansion from remote expansion and identify the remote OS, shell, path and privilege boundaries.\n2. Prefer established SSH host key verification and agent/key use; do not recommend disabling StrictHostKeyChecking to silence warnings.\n3. Treat server paths, quoting, globbing and leading dashes carefully. Avoid embedding secrets in commands, environment output or scripts.\n4. For rsync or other sync operations, show a dry run and exact source/destination interpretation (including trailing slashes) first.\n5. Handle copies, backups or deletions on remote systems as consequential writes requiring scope validation and user authorization.\n6. Report what has and has not been executed; include validation from the destination when possible.\n\n## Relevant references\n- Read `../../references/remote-operations.md` for domain-specific guidance.\n- Read `../../references/safety-risk-model.md` for domain-specific guidance.\n- Read `../../references/security-and-secrets.md` for domain-specific guidance.\n\n## Completion checks\n- Local vs remote quoting explicit\n- Host authenticity preserved\n- Dry run precedes remote mutation\n\n## Deliverable\nUse the minimum format that makes the answer actionable: the actual command or patch, platform assumptions, a preview before risky changes, and a reproducible validation step. Clearly label proposed actions versus observed execution.\n"
}