manage-nodeterm-canvas

Create, organize, and orchestrate agent nodes on the nodeterm canvas via CLI shim.

1|Updated Aug 17, 2026
One-click install
npx skills add https://github.com/Marshal-Nguyen/Skill_Claude_Agent --skill manage-nodeterm-canvas-marshal-nguyen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manage-nodeterm-canvas
Source: https://github.com/Marshal-Nguyen/Skill_Claude_Agent/tree/main/claude/skills/manage-nodeterm-canvas
Command: npx skills add https://github.com/Marshal-Nguyen/Skill_Claude_Agent --skill manage-nodeterm-canvas-marshal-nguyen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating multiple AI agent sessions (Claude, Codex, Gemini) across parallel workstreams is manual and error-prone; this Skill lets you programmatically open, group, link, and verify agent nodes on the nodeterm canvas from within a session. ## Core Features & Use Cases - Node lifecycle control: Open terminals, Claude/Codex/Gemini agent sessions, media viewers, and browsers; rename, arrange, align, write to, and close nodes. - Team orchestration: Spawn labeled agent teams with spawn-team, bind git worktrees to groups with open-worktree, and chain dependent stations with --after so downstream agents start when upstream ones go idle. - Verification panels: Run verify to open multi-lens review panels (correctness, security, tests) with a judge that merges findings into one verdict. - Use Case: Say "Build with Nodeterm orchestration" to split a feature into independent workstreams, each on its own branch and worktree group, then collect and synthesize results via linked context. ## Quick Start Ask the agent to build your task with Nodeterm orchestration, splitting the work into parallel agent stations on separate git worktrees.

Frequently Asked Questions about manage-nodeterm-canvas

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate multiple Claude agents in parallel with nodeterm?▼

Use spawn-team with a JSON array of roles and prompts to open one agent per role in a labeled group, or open-worktree per branch followed by open-agent with the group id. Each station works on its own branch, and you read results through the context links created automatically.

How do I make one nodeterm agent wait for another to finish?▼

Pass --after with the upstream node id when opening the downstream agent; it stays armed and launches itself once every listed station goes idle. Waiting only works on agent nodes that report status, not plain terminals.

Can I open Codex or Gemini sessions on the nodeterm canvas?▼

Yes, use open-agent with --agent codex, gemini, opencode, or a custom agent id, plus optional count, cwd, prompt, and group flags. Claude sessions can also be opened directly with open-claude.

Does manage-nodeterm-canvas work outside a nodeterm session?▼

No, the skill only works inside a controllable nodeterm Claude session. If the CLI reports canvas control is unavailable, the session cannot be controlled and retrying will not help.

Why does show-video or show-web fail in an SSH project?▼

In SSH projects, nodes run on the host but media viewers read the desktop's disk, so show-video and show-web with local files are refused for host paths. Use --url instead, or copy the file to the desktop first.

How do I verify an agent's work on the nodeterm canvas?▼

Run verify with the target node id to open a review panel: one reviewer per lens (default correctness, security, tests) armed behind the target, plus a judge that merges findings into a single verdict. Reviewers only read the work and do not modify files.