Update to Unix Copilot

{
  "description": "Improve slow shell pipelines using measured file size, I/O, process overhead and portable efficient techniques.",
  "included_files": [],
  "name": "performance-pipelines",
  "skill_md_contents": "---\nname: performance-pipelines\ndescription: Improve slow shell pipelines using measured file size, I/O, process overhead and portable efficient techniques.\n---\n\n# CLI performance and scale\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. Define performance goal and sample workload size, storage type and current observed timings. Do not invent benchmark numbers.\n2. Determine whether time is spent on process startup, repeated scans, buffering, decompression, disk I/O or CPU.\n3. Consider streaming, reducing unnecessary subprocesses, stable sort/locale and data-tool alternatives while preserving semantics.\n4. Avoid unbounded parallelism on shared hosts and memory-heavy commands on large files.\n5. Benchmark representative inputs under the same environment and check output correctness, not just speed.\n6. Document GNU/BSD compatibility and residual performance uncertainty.\n\n## Relevant references\n- Read `../../references/performance-pipelines.md` for domain-specific guidance.\n- Read `../../references/text-processing.md` for domain-specific guidance.\n- Read `../../references/portability-matrix.md` for domain-specific guidance.\n\n## Completion checks\n- Measured before-and-after when tools exist\n- Semantics preserved\n- Resource risk controlled\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"
}