tool-install

Install missing runtimes and tools in Copilot containers via pinned Nix and uv.

Updated May 10, 2026
One-click install
npx skills add https://github.com/rob-broadley/ai-airbase --skill tool-install
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tool-install
Source: https://github.com/rob-broadley/ai-airbase/tree/main/cadre/skills/tool-install
Command: npx skills add https://github.com/rob-broadley/ai-airbase --skill tool-install

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of choosing the correct, reproducible command to install tools inside the Copilot container, especially when you cannot use system package managers and you need consistent results across sessions.

Core Features & Use Cases

  • Nix-based bootstrapping: Install language runtimes, compilers, and non-PyPI tools using pinned nixpkgs attributes for reproducibility.
  • uv-based PyPI tooling: Install Python (and other PyPI-distributed) tools via uv tool install, including version-pinning and upgrades.
  • Global ecosystem installers without root: Use ecosystem-native installers (npm -g, go install, cargo install, dotnet tool install --global, etc.) after the runtime/toolchain is present.

This is used by bootstrap and specialist reviewer agents when they need to provision missing runtimes or install analysis/review tools that the container image does not yet have.

Quick Start

Ask the agent to look up how to install the required tool in the Copilot container environment using Nix or uv, and then follow the corresponding row from the tool-to-manager reference table.

Frequently Asked Questions about tool-install

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install missing language runtimes in a container without using system package managers?

To install missing language runtimes without system package managers, use Nix-based bootstrapping with pinned nixpkgs attributes. This enforces reproducibility by provisioning compilers and non-PyPI tools deterministically across sessions without requiring root access.

What is the best way to install Python tools reproducibly inside a Copilot container?

The best way to install Python tools reproducibly is using uv tool install with version-pinning. This uv-based approach ensures consistent PyPI package installation across container sessions, replacing non-deterministic pip installs for reliable tool provisioning.

Can I use global ecosystem installers like npm or cargo inside the Copilot container without root?

Yes, you can use ecosystem-native installers like npm -g, go install, cargo install, and dotnet tool install --global without root. After bootstrapping the runtime via Nix, these global installers provision ecosystem-specific tooling reliably.

Does tool-install support bootstrapping multiple language ecosystems like Go, Java, and Rust?

Yes, tool-install supports bootstrapping Node.js, Python, Java, C#, C++, Go, and Rust ecosystems. It applies a deterministic installation playbook using Nix-pinned runtimes and uv-based PyPI installs to provision missing toolchains across these languages.

Why should I use pinned nixpkgs attributes instead of standard package managers for container tool installation?

Pinned nixpkgs attributes enforce reproducible builds by locking exact dependency versions, unlike standard package managers that drift between sessions. This deterministic approach guarantees consistent runtime and tool provisioning across container environments.