Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

$pwd:

pi-package-sandbox-test

Name: Pi Package Sandbox Test
Author: spences10

// Use when verifying that published Pi packages from this repository install and load for normal Pi users without the repository wrapper. Applies to pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.

Ejecutar en Manus

$ git log --oneline --stat

stars:37

forks:7

updated:23 de mayo de 2026, 16:44

SKILL.md

readonly

name	pi-package-sandbox-test
description	Use when verifying that published Pi packages from this repository install and load for normal Pi users without the repository wrapper. Applies to 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

related-skills.json

mismo repositorio

pi-primitive-check.md

from "spences10/my-pi"

Compare proposed Pi customisation features with Pi built-in primitives before implementation. Applies to extensions, packages, slash commands, workflows, or speculative feature ideas.

2026-05-2537

pi-extension-development.md

from "spences10/my-pi"

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

2026-05-2337

pi-release-workflow.md

from "spences10/my-pi"

Prepare or verify releases for this Pi monorepo. Use for Changesets, pnpm lockfile/versioning, package preview generation, release-age policy, or published package installability checks.

2026-05-2337

pi-validation-flow.md

from "spences10/my-pi"

Validate Pi monorepo changes before reporting. Use after editing TypeScript, Svelte, package manifests, built-in registry, tests, or repo tooling.

2026-05-2337

package.json

"author": "spences10"

"repository": "spences10/my-pi"

Abrir repositorio de GitHub Ver repositorios del creador

$ install --global

$ download --local

Ejecutar en Manus

$ useful --forSOC

Analistas de garantía de calidad de software y probadoresOcupaciones informáticas y matemáticas15-1253L4

name	pi-package-sandbox-test
description	Use when verifying that published Pi packages from this repository install and load for normal Pi users without the repository wrapper. Applies to 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

pi-package-sandbox-test

Pi Package Sandbox Test

Procedure

Report Format

Failure Patterns

Más de este repositorio

Pi Package Sandbox Test

Procedure

Report Format

Failure Patterns

Más de este repositorio