Update to Unix Copilot

{
  "description": "Create, inspect, extract, restore and verify archives and backups using safe filesystem and portability practices.",
  "included_files": [],
  "name": "backups-and-archives",
  "skill_md_contents": "---\nname: backups-and-archives\ndescription: Create, inspect, extract, restore and verify archives and backups using safe filesystem and portability practices.\n---\n\n# Backups, archives and restoration\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. Identify data source, target filesystem, format, size, permissions, destination and restore objective.\n2. List archive members before extraction and screen for absolute paths, `..` traversal, unexpected symlinks and overwrite risks.\n3. Prefer a new extraction directory, restricted permissions and a backup before replacing existing files.\n4. For archive creation, verify paths, filters and exclusions; ensure the output archive is not accidentally included in itself.\n5. Include integrity checks (list, checksum, sample restore, counts) and clarify that a successful archive command is not equivalent to a tested recovery.\n6. For backups, describe schedule, retention, encryption and off-host copy only to the extent established.\n\n## Relevant references\n- Read `../../references/backups-and-archives.md` for domain-specific guidance.\n- Read `../../references/filesystem-operations.md` for domain-specific guidance.\n- Read `../../references/security-and-secrets.md` for domain-specific guidance.\n\n## Completion checks\n- No unsafe extraction to root\n- Restore test considered\n- Originals preserved before replacement\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"
}