Skip to content

docs: add agent skill for public O deploy + health validation - #3

Open
qianghan wants to merge 1 commit into
livepeer:mainfrom
qianghan:add-deploy-validation-skill
Open

docs: add agent skill for public O deploy + health validation#3
qianghan wants to merge 1 commit into
livepeer:mainfrom
qianghan:add-deploy-validation-skill

Conversation

@qianghan

Copy link
Copy Markdown

Why

The bundle deploys cleanly, but "did it work?" is the hard part — and the
current README.md validation (registration logs + /discovery reachable +
TLS up) is exactly the check a non-functional runner still passes.

In practice a Scope live runner can register, advertise capacity_available,
accept a session, and even bill the client — while producing zero frames.
The
orchestrator's /discovery returns 200, gateways route real traffic to it,
the per-session balance is debited by time×pixels (not by output), and every
stream silently black-holes. Surface checks stay green the whole time.

This PR adds an agent-runnable skill so Claude/Codex can both complete a
public-O deployment and prove it is genuinely serving video.

What

  • skills/deploying-scope-public-orchestrator/SKILL.mdagentskills.io
    format (name + description), usable by Claude and Codex.
    • Deploy essentials cross-referenced to README.md (no duplication).
    • Ordered, runnable validation that stops at the first failure:
      containers/healthcheck → go-livepeer /healthzmodels actually
      downloaded
      (/workspace/shared/models must hold real weights, not just
      lora/) → GPU/CUDA kernel sanityArbitrum RPC reachable (no 401
      flood) → /discovery advertises the runner → a real session produces
      frames
      (the decisive, sufficient check).
    • A Common Failures table of observed root causes (empty model prefetch /
      No artifacts defined, no kernel image is available for execution on the device, RPC 401 … does not have access to this network, trickle
      in=none, out=none / "stream disappeared", balance drained with no video,
      tunnel buffering).
    • A Red Flags list: do not report "healthy" from registration/discovery
      alone.
  • README.md — a short "For Agents (Claude / Codex)" pointer to the skill.

Grounding

The validation steps and failure table are derived from real observed failures
on a live public deployment (a runner that passed every README check yet never
produced a frame: empty model volume, CUDA arch mismatch, and a 401 RPC). The
skill exists to turn those into a repeatable, agent-driven health gate.

🤖 Generated with Claude Code

Add skills/deploying-scope-public-orchestrator/SKILL.md so agents (Claude,
Codex) can complete a public Scope orchestrator deployment and validate it is
genuinely online and healthy.

The skill's core point: a Scope live runner can register, advertise
capacity_available, accept a session, and bill the client while producing zero
frames. /discovery returning 200 is necessary but not sufficient. The skill
provides an ordered, runnable validation (containers -> healthz -> models
actually downloaded -> GPU/CUDA sanity -> RPC reachable -> discovery -> a real
session producing frames) plus a table of observed failure modes, so agents do
not report a non-functional runner as healthy.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: qianghan <infraservice@livepeer.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant