package-service

Provide a service name or upstream URL inside a StartOS packaging workspace. The workflow researches the upstream project, confirms the package shape with you once, scaffolds with start-cli s9pk init-package, then builds and verifies the .s9pk on a StartOS box.

A workspace is a directory containing .startos/ with build.key.pem or a schema-tagged config.yaml. Create one with start-cli s9pk init-workspace, which clones the guide checkout, writes AGENTS files, and generates a signing key.

A box is not required to build the package, but it is the only way to verify it. Without one, the Skill builds the .s9pk and reports plainly that the package has never run, handing the verification protocol to the user.

You need Docker, make, Node v22+, npm, mksquashfs, git, curl, jq, and start-cli. The Skill checks all of them at once and reports the exact install command for anything missing rather than installing silently.

The decision gate is the single planned interruption: it presents research findings and a recommended package shape so one round of answers settles image, interfaces, credentials, and backup strategy. After the gate, the build and verification run to completion without further input.