install-pi-extension

Install pi-mono or pi-agent extensions into OMP from npm, GitHub, or local folders.

Updated Jan 17, 2023
One-click install
npx skills add https://github.com/MjxOro/dotfiles --skill install-pi-extension
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: install-pi-extension
Source: https://github.com/MjxOro/dotfiles/tree/main/claude/.claude/skills/install-pi-extension
Command: npx skills add https://github.com/MjxOro/dotfiles --skill install-pi-extension

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Installing and managing pi-mono/pi-agent extensions into OMP from npm, GitHub, or local extension folders can be complex. This Skill standardizes the process, handles manifest compatibility, and patches legacy imports as needed to keep extensions functioning across environments.

Core Features & Use Cases

  • Install from npm packages that declare pi or omp manifests.
  • Install from GitHub repos or local extension folders and patch compatibility as required.
  • Validate install success, run compatibility patches, and list extension capabilities for quick verification.

Quick Start

Run install-pi-extension <source> to add a pi extension from npm, GitHub, or a local folder and patch legacy imports if needed.

Frequently Asked Questions about install-pi-extension

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

FAQPage Schema
How do I install pi-mono extensions into OMP from npm or GitHub?

To install pi-mono extensions into OMP, you provide an npm package, GitHub repo, or local folder source. The process automatically checks manifest compatibility and patches legacy imports to ensure the extension functions correctly.

What prerequisites are needed to install pi-agent extensions in OMP?

Installing pi-agent extensions requires an active OMP environment with bun and npm access. Additionally, a plugin installation directory must exist at ~/.omp, and the target package must contain a pi or omp manifest.

How does legacy-import patching work when adding pi extensions to OMP?

Legacy-import patching for pi extensions updates outdated import paths during the installation process. This compatibility check adjusts the extension code so it functions seamlessly across heterogeneous OMP environments.

Can I upgrade or remove existing pi-mono extensions from heterogeneous sources?

Yes, you can upgrade or remove existing pi-mono extensions from heterogeneous sources like npm and GitHub. The process manages the installation lifecycle and applies necessary manifest compatibility patches during upgrades.

Why does my pi extension installation fail when missing a manifest?

Pi extension installation fails without a manifest because the process requires a pi or omp manifest in the target package. This manifest guides proper installation and performs the necessary legacy-import patching.

What is the best way to verify pi extension capabilities after installation?

The best way to verify pi extension capabilities is to use the validation feature post-installation. This validates install success, runs compatibility patches, and lists extension capabilities for quick verification.