skills.rest
ivy
ivyCOMMUNITY
Explore all skills by this author →
GitHub

install

Automate software package installation and configuration across mise, npm, pip, and brew backends.

9|Updated Jul 15, 2025
Search Tags:#automation#npm#mise#installation#package-management#brew
One-click install
npx skills add https://github.com/ivy/dotfiles --skill install-ivy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: install
Source: https://github.com/ivy/dotfiles/tree/main/.claude/skills/install
Command: npx skills add https://github.com/ivy/dotfiles --skill install-ivy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the installation and configuration of software packages across multiple backends, reducing manual setup and ensuring repeatable environments.

Core Features & Use Cases

  • Identify package type across mise registry, known GUI/apps (brew), and other backends, mapping to the correct installation target (Aqua registry, GitHub releases, Python, Node, or system utilities).
  • Discover latest or exact versions using gh release view, npm view, pip index versions, or native mise commands.
  • Update manifests under home/dot_config/mise/config.toml and home/.chezmoidata/packages.yaml with exact version pins, then verify with chezmoi diff, apply with user approval, and commit changes per package.

Quick Start

Provide one or more package names to install and let the skill locate versions, update manifests, and apply changes.

Frequently Asked Questions about install

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

FAQPage Schema
How do I automate package installation across multiple backends like npm and brew?▼

Automating package installation across multiple backends involves mapping package names to the correct installation target, resolving exact versions via npm view or gh release view, and updating manifests. The process requires user approval before applying changes to ensure safe configuration.

What is the best way to manage exact version pins for CLI tools using mise?▼

Managing exact version pins using mise requires updating the config.toml manifest with the resolved version numbers. This ensures repeatable environments by enforcing strict version control across your development tools and preventing unexpected upgrades during automated installations.

How do I update package manifests and verify changes before applying them?▼

Updating package manifests involves writing exact version pins to config.toml and packages.yaml. You verify the pending configuration changes using chezmoi diff, apply them only after explicit user approval, and commit the changes per package to maintain an auditable history.

Does this package installation automation work with Python and Node backends?▼

Yes, this package installation automation works with Python and Node backends. It identifies package types across the mise registry and maps them to the correct installation target, discovering versions using pip index versions or npm view to update manifests accurately.

Can I use this to install system utilities and GUI apps from GitHub releases?▼

Yes, you can use this to install system utilities and GUI apps. The automation identifies known GUI apps via brew and maps packages to GitHub releases, using gh release view to discover the latest versions before updating your configuration manifests.

Related Skills

Explore More Software Engineering Skills→
martinemdemartinemde
9

managing-chezmoi-packages

Manage packages and external dependencies in a chezmoi dotfiles repository.

Community
Advanced
lightvu25lightvu25

package-remove

Remove a Unity package from manifest.json and trigger package resolution.

Community
Intermediate
HazATHazAT
947

release

Automate versioned npm package releases with changelog generation and GitHub releases.

Community
Intermediate
carapace-shcarapace-sh
1.9k

winget

Manage Windows software packages using the Winget Package Manager CLI.

Official
Advanced