Update to Unix Copilot

{
  "description": "Inspect and reason about Unix permissions, ownership, ACLs, process signals and services with least-privilege guidance.",
  "included_files": [],
  "name": "permissions-and-processes",
  "skill_md_contents": "---\nname: permissions-and-processes\ndescription: Inspect and reason about Unix permissions, ownership, ACLs, process signals and services with least-privilege guidance.\n---\n\n# Permissions, processes and services\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 whether the task concerns file mode bits, ownership, ACLs, process state, ports or services; do not apply one fix to all problems.\n2. Gather read-only evidence (`ls -l`, `stat`, `id`, `ps`, `lsof` or service manager output) using platform-correct syntax.\n3. For access errors, determine the expected principal and minimum needed permissions; never default to `chmod -R 777`.\n4. For signals, process termination or service restarts, identify PID/service accurately and assess dependent workloads. Preview candidate processes before any kill.\n5. Separate investigation, proposed change and validation. Elevate privileges only for the precise step requiring it.\n6. Plan rollback or recovery for permission changes and service interruption where feasible.\n\n## Relevant references\n- Read `../../references/permissions-and-processes.md` for domain-specific guidance.\n- Read `../../references/safety-risk-model.md` for domain-specific guidance.\n- Read `../../references/diagnostics-playbook.md` for domain-specific guidance.\n\n## Completion checks\n- Least privilege\n- Correct service manager for platform\n- Exact target and side effects documented\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"
}