mcpField
P
pi-package-authoring

pi-package-authoring

github.com/romiluz13Agent workflows2071 installsUpdated 28w ago
Repository

About pi-package-authoring

A Pi skill for authoring packages and understanding how their resources are resolved. It guides package layout, precedence, and security considerations using Pi documentation and source references.

Key features

  1. 01Package manifest guidance
  2. 02Conventional directory guidance
  3. 03Resource precedence analysis
  4. 04Package security notes

Use cases

  1. 01Drafting a Pi package manifest
  2. 02Checking package resource overrides
  3. 03Reviewing third-party package risks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/romiluz13/pi-agent-skills --skill pi-package-authoring

After installing, type/pi-package-authoringin Claude Code to confirm it loaded.

Bundled filesreferences/CORPUS.md

Details

From the project README

Pi package authoring

Grounding

  1. pi-mono/packages/coding-agent/docs/packages.md — manifest, install commands, layout.
  2. pi-mono/packages/coding-agent/README.md — Pi Packages section (pi install, package.json pi key, keywords).
  3. pi-mono/packages/coding-agent/src/core/package-manager.ts — resourcePrecedenceRank (package-origin resources sort after user/project).

Invariants

  • Packages integrate through the same resource resolution pipeline as local dirs; package-origin metadata ranks after user/project auto paths — see resourcePrecedenceRank in pi-mono/packages/coding-agent/src/core/package-manager.ts.
  • Third-party packages execute code; skills can instruct arbitrary actions — security notes are first-party in docs/packages.md and coding-agent README.

Workflows

  • Define a package: Mirror the package.json example from docs/packages.md / README; verify conventional dirs (skills/, extensions/, etc.) against those docs.
  • Predict overrides: Combine package-manager precedence with loadSkills “first name wins” (pi-mono/packages/coding-agent/src/core/skills.ts).

Anti-patterns

  • Do not invent CLI flags not documented in docs/packages.md / README.

Comments

Markdown supported