Run any Skill in Manus with one click

pi-package-sandbox-test

Stars81

Forks12

UpdatedJune 1, 2026 at 20:15

Use when verifying that published Pi packages install and load for normal users, including pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

spences10

spences10/my-pi

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	pi-package-sandbox-test
description	Use when verifying that published Pi packages install and load for normal users, including pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.
compatibility	Requires Node.js, pnpx, network access, ralph-town Daytona sandbox access, npm registry access, and vanilla Pi via @earendil-works/pi-coding-agent.

Pi Package Sandbox Test

Verify published packages work for normal Pi users, independent of my-pi.

Procedure

From the repository root, enumerate packages/*/package.json.
Select only packages with a pi manifest; helper/internal packages without pi are not user-installable Pi packages.
For each selected package, compare local package.json version with npm view <pkg> version.
In a disposable Daytona sandbox via pnpx ralph-town run, use vanilla Pi only:
```
pnpx @earendil-works/pi-coding-agent
```

For each published npm version, verify both commands succeed:

pnpx @earendil-works/pi-coding-agent install npm:<package>@<npm-version>
pnpx @earendil-works/pi-coding-agent -e npm:<package>@<npm-version> --help

In the same clean sandbox config, install all selected packages together, then run:

pnpx @earendil-works/pi-coding-agent list
pnpx @earendil-works/pi-coding-agent --help

Report Format

Report a compact table with:

package name
local version
npm version
install result
ephemeral load result
notes

Call out local/npm version drift separately. Version drift is not a failure when it is explained by release timing, changesets, or minimumReleaseAge; the user-facing check should use the published npm version that normal Pi users can install.

Failure Patterns

Treat these as failures unless explained by the sandbox environment:

npm package cannot be resolved
pi install npm:<package>@<version> exits non-zero
pi -e npm:<package>@<version> --help exits non-zero
startup output includes Cannot find module, ERR_MODULE_NOT_FOUND, SyntaxError, TypeError, or ReferenceError
packages pass alone but fail when installed together

More from this repository

same repository

execute-harness

spences10/my-pi

Use when running an existing /tmp Pi task harness. Executes inside the active contract, records status, respects enforcement, and loops through validation.

2026-07-0481

create-harness

spences10/my-pi

Use when creating executable /tmp Pi task harnesses for ambiguous or high-risk coding work. Builds contract, prompts, validation, logs, and enforcement rules.

2026-06-2881

review-harness

spences10/my-pi

Use when reviewing implementation work that ran through a /tmp Pi task harness. Checks contract drift, unsafe shortcuts, validation evidence, and status honesty.

2026-06-2881

pi-observability-local-dev

spences10/my-pi

Use when developing or reviewing packages/pi-observability dashboard/server changes locally, especially rebuilding dist, restarting the 43190 server, validating UI behavior, or keeping the local dashboard in sync with source edits.

2026-06-2581

pi-primitive-check

spences10/my-pi

Use when evaluating proposed Pi customisation work against built-in Pi primitives before implementation, especially extensions, packages, slash commands, and workflow ideas.

2026-06-0781

pi-extension-development

spences10/my-pi

Use when creating or modifying Pi extensions, built-in extension wiring, prompt shims, package scaffolds, package READMEs, or packages/pi-* implementation in this monorepo.

2026-06-0181

name	pi-package-sandbox-test
description	Use when verifying that published Pi packages install and load for normal users, including pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.
compatibility	Requires Node.js, pnpx, network access, ralph-town Daytona sandbox access, npm registry access, and vanilla Pi via @earendil-works/pi-coding-agent.

Pi Package Sandbox Test

Verify published packages work for normal Pi users, independent of my-pi.

Procedure

From the repository root, enumerate packages/*/package.json.
Select only packages with a pi manifest; helper/internal packages without pi are not user-installable Pi packages.
For each selected package, compare local package.json version with npm view <pkg> version.
In a disposable Daytona sandbox via pnpx ralph-town run, use vanilla Pi only:
```
pnpx @earendil-works/pi-coding-agent
```

For each published npm version, verify both commands succeed:

pnpx @earendil-works/pi-coding-agent install npm:<package>@<npm-version>
pnpx @earendil-works/pi-coding-agent -e npm:<package>@<npm-version> --help

In the same clean sandbox config, install all selected packages together, then run:

pnpx @earendil-works/pi-coding-agent list
pnpx @earendil-works/pi-coding-agent --help

Report Format

Report a compact table with:

package name
local version
npm version
install result
ephemeral load result
notes

Failure Patterns

Treat these as failures unless explained by the sandbox environment:

npm package cannot be resolved
pi install npm:<package>@<version> exits non-zero
pi -e npm:<package>@<version> --help exits non-zero
startup output includes Cannot find module, ERR_MODULE_NOT_FOUND, SyntaxError, TypeError, or ReferenceError
packages pass alone but fail when installed together