Menu
Gets detailed status and output of a specific examiner task on a playground. Use to debug why a task is failing.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Debugs an existing challenge by starting it, inspecting tasks, troubleshooting over SSH, fixing source files, and restarting. Use when a challenge's tasks are failing or hanging.
Lists all examiner tasks (init and regular) for a playground. Use to check the status of challenge/tutorial tasks.
Executes a command on a playground VM via SSH. Use when you need to run commands on a playground for testing, debugging, or verification.
Applies a scripted solution to a running challenge (single- or multi-VM) and verifies every non-helper task completes. Use to validate a .solution.sh / .solution-NN.sh end-to-end.
Starts a challenge playground session. Use when you need to launch a challenge for testing or solving.
Stops the current solution attempt for a challenge. Use when you need to stop a running challenge.
| name | get-playground-task |
| description | Gets detailed status and output of a specific examiner task on a playground. Use to debug why a task is failing. |
| argument-hint | <playground-id> <task-name> |
Get detailed information about examiner task $1 on playground $0.
Use the API path — it needs no SSH tunnel, covers all machines at once
(including noSSH ones), and includes each task's status plus the stdout/stderr
(and hintcheck/failcheck output) of its last execution:
labctl playground tasks $0 -o yaml
Grep for $1 in that output to find the specific task. This reports the last run
only; it does not trigger a fresh run. Prefer this over labctl ssh $0 -- examinerctl task get $1 — the SSH form shows a single machine and burns a tunnel
slot, whereas the YAML API form gives the same per-task output for every machine
without SSH.
examinerctl task wait does not trigger, start, or re-run anything — there is no
task start/task run, and you cannot manually fire a task. The examiner evaluates
the task on its own; task wait just blocks until it reaches a terminal state
(pass/fail) or the timeout expires. This is the one task operation the API can't do:
labctl ssh $0 -- examinerctl task wait $1 --timeout 120s
Use it to block after setting up a task's preconditions — e.g. a .solution-NN.sh
ends with examinerctl task wait <verify-task> so applying the solution blocks until
that task has settled.
completed 40 or failed
35) and never runs again, even if the world state later changes. The status
only ever goes up — a passed task cannot later fail — so a single completed
observation is authoritative.examinerctl ... call opens an SSH tunnel. Use the
tunnel-free labctl playground tasks $0 -o yaml for inspection and polling, and
never put labctl ssh -- examinerctl task wait inside a backgrounded retry
loop — orphaned ssh children exhaust the tunnel pool (see the SSH tunnel
discipline notes in run-playground-command).