pi-vendor

Vendor installed Pi extensions into the agents repository with minimal copied files.

1|1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/luan/agents --skill pi-vendor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pi-vendor
Source: https://github.com/luan/agents/tree/main/.agents/skills/pi-vendor
Command: npx skills add https://github.com/luan/agents --skill pi-vendor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of integrating an installed Pi extension into the agents repository so it works reliably without requiring global installs.

Core Features & Use Cases

  • Targeted extension vendoring: Copies only the runtime files required by the Pi extension entrypoint into pi/agent/extensions/<extension-name>/.
  • Lean dependency relocation: Moves only necessary third-party runtime dependencies into the repo root package.json for reproducible installs.
  • Pi settings integration: Updates pi/agent/settings.json to reference the vendored extension or relies on auto-discovery when index.ts exists.
  • Validation-focused workflow: Guides you through installing, running just validate, and performing an offline Pi load smoke test.

Quick Start

Tell the AI: "Vendor the installed Pi package npm:pi-web-access into this agents repo, preserving only required runtime files, updating package.json dependencies, and configuring pi/agent/settings.json, then run the offline Pi smoke test."

Frequently Asked Questions about pi-vendor

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

FAQPage Schema
How do I vendor a Pi extension into my repository for offline use?

To vendor a Pi extension, copy only the required runtime files into pi/agent/extensions, relocate third-party dependencies to the root package.json, and update pi/agent/settings.json for the Pi agent runtime.

What does extension vendoring do with node dependencies?

Extension vendoring relocates only the necessary third-party runtime node dependencies from the installed extension into the repo root package.json, ensuring reproducible installs without requiring global installs.

Do I need to update settings.json when adding a Pi extension to my repo?

You must update pi/agent/settings.json to reference the vendored extension, unless an index.ts file exists at the extension path, which allows the Pi agent runtime to auto-discover it automatically.

Can I customize or fork an installed Pi extension and keep only the runtime files?

Yes, extension vendoring supports customization, localization, and forking by identifying pi.extensions entrypoints and copying only the imported runtime files into pi/agent/extensions for the repo.

How do I validate a vendored Pi extension works offline?

Validate the vendored Pi extension by running just validate and performing an offline Pi load smoke test to ensure dependency correctness and reliable loading without global installs.

Why does my Pi extension fail to load offline in the agent runtime?

Offline Pi extension loading fails when runtime dependencies are missing from the root package.json or settings.json is not updated, preventing the Pi agent runtime from locating the required files.