PUBLIC MARKETING + DOCS · HTTPS VERIFIED. The skill describes the verified localhost service workflow; API, Player, release hosts, and protected content remain undeployed in production, and npm packages remain unpublished.

path: /skill/ · skill version 0.2.0view as markdown →

skill · agent operating contract

Load the safe path before operating ScreenRig.

ScreenRig is an agent-operated digital-signage service: an agent uses the CLI and REST API to upload content, assemble a looping playlist, pair a browser screen, and observe the result.

download SKILL.md

What it teaches

  • Discover current commands from CLI help and HTTP schemas from the raw OpenAPI contract.
  • Build the checkout CLI, create and acknowledge an account credential, package/upload an app, publish immutable content, create a playlist, pair a Player, assign the playlist, and follow durable events.
  • Preserve the account/runtime/release authority split and avoid treating protected storage as public hosting.
  • Retry safely with idempotency keys and revisions; recover from durable operation, cursor, and problem responses.

Phase truth

SurfaceStatus
CLI, SDK, Player, backendVerified on the full three-replica localhost lifecycle
Android sourceStandard/managed/Amazon unit, lint, debug, R8 release, and Player integration pass; no KVM instrumentation, physical hardware validation, store publication, or general offline guarantee
npm packagesNot published
Marketing + docsPublic HTTPS live and verified; not an uptime, SLA, customer, or traffic claim
Service productionAPI, Player, release hosts, protected content, and full stack not deployed or verified
MCP / billing / screenshots / recoveryDeferred beyond v1

Safe verification

shell · no guessed package install
node packages/cli/dist/bin.js --help
node packages/cli/dist/bin.js app pack ./path/to/built-webapp --output /tmp/app.tar.gz

The first command inspects the implemented command tree. The second packages local content without contacting a backend. Do not install an unrelated npm package named screenrig.

Hard rules

  • Never place account bearer tokens in URLs, Player state, uploaded applications, logs, or examples.
  • Never invent public API availability from localhost evidence.
  • Never construct release or media URLs from identifiers; follow server-issued manifests and grants.
  • Never describe protected release/media/K/V origins as public file hosting.
  • Use the OpenAPI contract for HTTP schema and CLI --help for commands.