Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

drive-running-node

Étoiles6

Forks0

Mis à jour23 juillet 2026 à 23:12

Resolve exactly one running StreamLib node and health-check it with a live `graph` round-trip, then pin its `--url` / `--node` so every following control verb targets the same node. Use at the start of a session against a running app — after `discover-running-nodes`, or whenever you are about to inspect, tap, submit, replace, connect, or capture and need a confirmed target locked in. Wraps `streamlib nodes` then `streamlib graph`.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

tatolab

tatolab/streamlib

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name

drive-running-node

description

drive-running-node

Turns "some node is running" into "this specific node answers, and here is how I address it." A graph call is the cheapest full control-plane round-trip, so it doubles as the health check: if graph returns the live topology, the node is drivable.

Steps

1. Find the candidates

streamlib nodes

Read the RUNTIME_ID and CONTROL_URL of the row you want (see discover-running-nodes for the columns). Copy one identifier — either the runtime_id (for --node) or the control_url (for --url).

2. Health-check + pin the target

Pick ONE addressing form and reuse it verbatim on every later verb:

By registry runtime_id:

streamlib graph --node <runtime_id>

By explicit control URL:

streamlib graph --url <control_url>

If exactly one node is live, both flags may be omitted and the resolver uses that sole node:

streamlib graph

A JSON graph dump (processors, links, states, metrics) means the node is healthy and the address is good. A non-zero exit means it is not drivable:

no live StreamLib nodes found — nothing is running; start a node.
N live nodes found; disambiguate with --node ... or --url ... — more than one is live and you passed neither flag; re-run with a specific --node/--url.
no registered node with runtime_id <id> — the --node value is wrong or the node exited; re-run streamlib nodes.
A transport/HTTP error — the endpoint is unreachable or auth failed (set STREAMLIB_MCP_TOKEN).

3. Pin it for the rest of the session

Record the chosen --node <runtime_id> (preferred — stable across a port change) or --url <control_url>, and pass the same flag to every subsequent verb (inspect-live-graph, tap-live-channel, author-and-submit-processor, hot-swap-live-processor, capture-node-evidence, teardown-running-node).

Notes

Prefer --node <runtime_id> over --url when several nodes may be live — it is unambiguous and survives the ApiServer's port auto-increment.
STREAMLIB_MCP_TOKEN, when set, rides as the bearer token on the round-trip; export it once for the whole session.

Plus depuis ce dépôt

même dépôt

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

drive-running-node

description

drive-running-node

Steps

1. Find the candidates

streamlib nodes

2. Health-check + pin the target

Pick ONE addressing form and reuse it verbatim on every later verb:

By registry runtime_id:

streamlib graph --node <runtime_id>

By explicit control URL:

streamlib graph --url <control_url>

If exactly one node is live, both flags may be omitted and the resolver uses that sole node:

streamlib graph

A JSON graph dump (processors, links, states, metrics) means the node is healthy and the address is good. A non-zero exit means it is not drivable:

no live StreamLib nodes found — nothing is running; start a node.
N live nodes found; disambiguate with --node ... or --url ... — more than one is live and you passed neither flag; re-run with a specific --node/--url.
no registered node with runtime_id <id> — the --node value is wrong or the node exited; re-run streamlib nodes.
A transport/HTTP error — the endpoint is unreachable or auth failed (set STREAMLIB_MCP_TOKEN).

3. Pin it for the rest of the session

Notes

Prefer --node <runtime_id> over --url when several nodes may be live — it is unambiguous and survives the ApiServer's port auto-increment.
STREAMLIB_MCP_TOKEN, when set, rides as the bearer token on the round-trip; export it once for the whole session.