package-management

Orchestrate language runtime, package, and system dependency installations across projects.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/koya-alt/Catalyst --skill package-management-koya-alt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: package-management
Source: https://github.com/koya-alt/Catalyst/tree/main/local/skills/package-management
Command: npx skills add https://github.com/koya-alt/Catalyst --skill package-management-koya-alt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Project setup often requires manual, error-prone installation of language runtimes, package managers, and system dependencies. This skill provides a unified approach to manage these components across environments.

Core Features & Use Cases

  • Install and manage language runtimes (Python, Node.js, etc.)
  • Install language packages (pip, npm, cargo, etc.) and remove them
  • Install system dependencies via Nix and ensure project files reflect changes
  • Upgrade or remove dependencies while keeping project configurations in sync

Quick Start

Install Python and Node.js runtimes and common language packages for your project.

Frequently Asked Questions about package-management

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

FAQPage Schema
How do I install and manage Python and Node.js runtimes across different environments?

You can install and manage Python and Node.js runtimes by orchestrating installation across development, CI, and deployment environments with safe defaults. This approach enforces installation order, validates inputs, and automatically updates project files to reflect runtime changes.

What's the best way to install system dependencies via Nix and keep project files in sync?

Installing system dependencies via Nix ensures project files reflect changes automatically. This unified approach validates inputs, applies safe defaults, and updates configurations during installation to keep dependencies synchronized across development and deployment environments.

Can I use this approach to upgrade or remove npm and pip packages without breaking project configurations?

Yes, upgrading or removing npm and pip packages keeps project configurations in sync. It enforces correct installation order, validates inputs before changes, and applies safe defaults to prevent configuration drift during dependency removal or upgrades.

Does this package management method support installing cargo packages alongside npm and pip?

Yes, it supports installing cargo packages alongside npm and pip. It orchestrates multiple language-specific package managers, validates all inputs, enforces safe installation order, and updates project files to accurately reflect the newly added cargo dependencies.

Why does manual package installation fail in CI environments and how does orchestration fix it?

Manual package installation fails in CI environments due to error-prone setup and missing system dependencies. Orchestration fixes this by enforcing installation order, validating inputs, applying Nix-based system requirements, and synchronizing project files across all environments.

When do I need to validate inputs and enforce installation order for runtime dependencies?

You need to validate inputs and enforce installation order whenever installing language runtimes, language-specific packages, or system dependencies. This prevents configuration errors and ensures project files remain synchronized across development, CI, and deployment contexts.