Update to Unix Copilot

{
  "description": "Diagnose PATH, shell startup, interpreters, package managers and installed command versions on Linux or macOS.",
  "included_files": [],
  "name": "packages-and-environment",
  "skill_md_contents": "---\nname: packages-and-environment\ndescription: Diagnose PATH, shell startup, interpreters, package managers and installed command versions on Linux or macOS.\n---\n\n# Install and environment guidance\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. Inspect OS/release, shell, architecture, command location, version and whether a tool is already installed, using read-only checks.\n2. Identify the relevant package manager; avoid mixing apt, dnf, pacman, brew, pipx or project environment commands.\n3. Verify current official package and installation instructions before offering version-sensitive commands.\n4. Explain PATH precedence, login/nonlogin shells, startup files and potential duplicate environment entries.\n5. Minimize privileges; avoid blind installers and `sudo pip`, and never ask to paste credentials into shell history.\n6. After an installation or change, suggest `command -v`, version and small functionality checks. Do not claim success without output.\n\n## Relevant references\n- Read `../../references/install-environments.md` for domain-specific guidance.\n- Read `../../references/portability-matrix.md` for domain-specific guidance.\n- Read `../../references/security-and-secrets.md` for domain-specific guidance.\n\n## Completion checks\n- OS-appropriate package manager\n- No unnecessary privilege\n- Checks confirm executable and version\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"
}