메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when running an existing /tmp Pi task harness. Executes inside the active contract, records status, respects enforcement, and loops through validation.
Use when creating executable /tmp Pi task harnesses for ambiguous or high-risk coding work. Builds contract, prompts, validation, logs, and enforcement rules.
Use when reviewing implementation work that ran through a /tmp Pi task harness. Checks contract drift, unsafe shortcuts, validation evidence, and status honesty.
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.
Use when evaluating proposed Pi customisation work against built-in Pi primitives before implementation, especially extensions, packages, slash commands, and workflow ideas.
Use when creating or modifying Pi extensions, built-in extension wiring, prompt shims, package scaffolds, package READMEs, or packages/pi-* implementation in this monorepo.
| 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. |
Verify published packages work for normal Pi users, independent of
my-pi.
packages/*/package.json.pi manifest; helper/internal packages
without pi are not user-installable Pi packages.package.json version
with npm view <pkg> version.pnpx ralph-town run, use
vanilla Pi only:
pnpx @earendil-works/pi-coding-agent
pnpx @earendil-works/pi-coding-agent install npm:<package>@<npm-version>
pnpx @earendil-works/pi-coding-agent -e npm:<package>@<npm-version> --help
pnpx @earendil-works/pi-coding-agent list
pnpx @earendil-works/pi-coding-agent --help
Report a compact table with:
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.
Treat these as failures unless explained by the sandbox environment:
pi install npm:<package>@<version> exits non-zeropi -e npm:<package>@<version> --help exits non-zeroCannot find module,
ERR_MODULE_NOT_FOUND, SyntaxError, TypeError, or
ReferenceError