Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

discover-running-nodes

Estrellas6

Forks0

Actualizado23 de julio de 2026 a las 23:12

Enumerate the live StreamLib runtimes reachable over their control plane so you can pick a target before running any other control verb. Use when you need to know which running nodes exist — after `cargo run`-ing an example app in a worktree, when a control verb errors that zero or more-than-one node is live, or any time you must resolve a `runtime_id` / `control_url` to drive. Wraps `streamlib nodes` only.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

tatolab

tatolab/streamlib

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name

discover-running-nodes

description

discover-running-nodes

The entry point for every control-verb workflow: list the running nodes so a later verb can target one. A StreamLib node appears here only if its graph hosts an @tatolab/api-server/ApiServer processor — that processor is what binds a POST /mcp control endpoint and registers the node under $XDG_RUNTIME_DIR/streamlib/nodes/<runtime_id>.json. A runtime with no control endpoint is intentionally absent, not missing.

Steps

1. List the nodes

streamlib nodes

This scans the registry, liveness-checks every entry (a graph control-plane round-trip plus, on unix, a host-pid check), prunes the entries that are definitively gone (unreachable AND no live pid), and prints an aligned table:

RUNTIME_ID  CONTROL_URL            PID    ALIVE?  HINT
Rabc123     http://127.0.0.1:8080  12345  yes     streamlib (/path/to/app)

RUNTIME_ID — pass to any control verb as --node <runtime_id>.
CONTROL_URL — pass to any control verb as --url <control_url> (its POST /mcp base).
PID — the host process; teardown-running-node signals this to stop the node.
ALIVE? — control-plane reachability (yes means a graph round-trip answered). An entry can show no transiently (pid still alive, control plane briefly slow) without being pruned.
HINT — a human breadcrumb (e.g. the app's cwd).

2. Read the outcome

One yes row — that is your target; control verbs with neither --url nor --node default to this sole live node, so you can often skip pinning entirely.
Several yes rows — pick one and pin it with --node <runtime_id> (or --url) on every subsequent verb; a verb given neither flag with more than one live node errors and lists the candidates.
No running nodes found — start a node first (cargo run an example app whose graph hosts an ApiServer processor), then re-run.

Notes

No flags. streamlib nodes takes none.
When the control plane requires auth, export STREAMLIB_MCP_TOKEN before running — it rides the liveness probe (and every control verb) as an authorization: Bearer header.
To pin the chosen target and health-check it in one move, hand off to drive-running-node.

Más de este repositorio

mismo repositorio

milestone-loop

tatolab/streamlib

Run one reconciler pass of the standing milestone-loop — the turn procedure each `/work-on-milestone` firing invokes. Use when a loop firing (or the owner directly) needs to move the focused milestone one bounded step toward "merged, or waiting on the owner or on blockers." Checks the kill switch, probes rig capability, launches the milestone-loop workflow, and surfaces anything needing the owner. To START the loop on a milestone rather than run a single pass, use work-on-milestone.

2026-07-256

work-on-milestone

tatolab/streamlib

Drive a whole milestone to done with the standing loop — resolve the milestone, set the goal, and register the recurring reconciler that runs passes until every issue is merged or parked. Use when the owner says "work on <milestone>", "start the loop on <milestone>", "close out <milestone>", or wants the loop running without hand-typing a /loop invocation. Also the place to stop or re-target a running milestone driver.

2026-07-256

work-on-ticket

tatolab/streamlib

Take one ticket end-to-end in the current session with the owner present — the interactive counterpart to the standing loop. Use when they say "work on issue N", "let's do this ticket", "pick up X and I'll answer questions as you go", or want to drive a single issue to a PR now. Same workflow, same composed stages, same verifier as the loop — but questions come inline instead of parking.

2026-07-256

loop-status

tatolab/streamlib

Render the milestone-loop's current picture into one status board — what it's acting on, what's waiting on the owner (oldest first), what it's watching, recent outcomes, and spend. Use when asked "what's the loop doing", "loop status", "what's waiting on me", or before deciding whether to nudge or pause the loop. Read-only — it reports, it never acts.

2026-07-256

draft-design

tatolab/streamlib

Architecture-first entry point — recon the current code with the relevant domain experts, then produce a design brief for the owner (mermaid diagram, trade-offs, decisions taken, and an explicit decisions-for-owner list) posted to the issue. Use before building anything engine-zone, when a feature needs a shape decided, or when the owner asks to "design X first" or "draft the approach for this issue". Nothing builds until they approve in a comment.

2026-07-246

author-and-submit-processor

tatolab/streamlib

Write a brand-new processor from source and submit it into a running StreamLib node as a fresh instance, optionally wiring its ports to existing processors in one transactional step, then confirm it landed and is producing. Use when adding a new stage to a live pipeline during development — a new filter, sink, or generator — without restarting the app. Wraps `streamlib submit` then `graph` + `tap` to confirm.

2026-07-236

name

discover-running-nodes

description

discover-running-nodes

Steps

1. List the nodes

streamlib nodes

RUNTIME_ID  CONTROL_URL            PID    ALIVE?  HINT
Rabc123     http://127.0.0.1:8080  12345  yes     streamlib (/path/to/app)

RUNTIME_ID — pass to any control verb as --node <runtime_id>.
CONTROL_URL — pass to any control verb as --url <control_url> (its POST /mcp base).
PID — the host process; teardown-running-node signals this to stop the node.
ALIVE? — control-plane reachability (yes means a graph round-trip answered). An entry can show no transiently (pid still alive, control plane briefly slow) without being pruned.
HINT — a human breadcrumb (e.g. the app's cwd).

2. Read the outcome

One yes row — that is your target; control verbs with neither --url nor --node default to this sole live node, so you can often skip pinning entirely.
Several yes rows — pick one and pin it with --node <runtime_id> (or --url) on every subsequent verb; a verb given neither flag with more than one live node errors and lists the candidates.
No running nodes found — start a node first (cargo run an example app whose graph hosts an ApiServer processor), then re-run.

Notes

No flags. streamlib nodes takes none.
When the control plane requires auth, export STREAMLIB_MCP_TOKEN before running — it rides the liveness probe (and every control verb) as an authorization: Bearer header.
To pin the chosen target and health-check it in one move, hand off to drive-running-node.