install-package

Add development tools to managed package manifests and install them via the mt tool workflow.

Updated May 15, 2026
One-click install
npx skills add https://github.com/t-miura-024/tools --skill install-package-t-miura-024
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: install-package
Source: https://github.com/t-miura-024/tools/tree/main/.opencode/skills/install-package
Command: npx skills add https://github.com/t-miura-024/tools --skill install-package-t-miura-024

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the complexity of adding development tools by managing package manifests, selecting the right package manager, and running the project installation workflow safely.

Core Features & Use Cases

  • Package Discovery and Recommendation: Checks official Homebrew, Mise, and npm sources to determine supported installation options and recommend the best fit.
  • Manifest Management: Adds packages to the correct managed manifest while preventing duplicates and preserving repository conventions.
  • Safe Installation Workflow: Reviews changes, requests approval, executes the project tool installer, and handles failures with recovery options.

Quick Start

Ask the install-package skill to add the requested development tool to the managed package configuration and install it.

Frequently Asked Questions about install-package

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

FAQPage Schema
How do I add a new development tool to a managed package manifest?

Choosing between Homebrew, Mise, and npm for package installation involves evaluating which source officially supports the requested tool and matches your repository conventions. This skill automates that evaluation by checking all three sources and recommending the best fit.

How are duplicate package entries handled during manifest updates?

Duplicate package entries are prevented during manifest updates by detecting existing configurations before adding new tools. The skill preserves repository conventions by verifying the current state of the manifest and only applying approved changes.

What is the safest way to install development tools without breaking my environment?

The safest way to install development tools is through a controlled workflow that reviews manifest changes, requests explicit approval, and executes the installation via the repository-controlled mt tool install process. This approach includes failure handling and recovery options.

Does this package installation workflow require approval before modifying manifests?

Yes, the package installation workflow requires explicit approval before modifying manifests and executing the tool installer. It reviews the proposed changes to your configuration files first, ensuring you maintain control over repository state.

Why should I use a manifest-based approach instead of installing packages directly?

A manifest-based approach ensures tools are evaluated across Homebrew, Mise, and npm before installation, maintaining consistency across developer environments. It prevents untracked installations by routing everything through a repository-controlled workflow.