Agent skill

Nodetool API Reference

by nodetool-ai in nodetool-ai/nodetool

Integrate with NodeTool over REST, tRPC, MsgPack WebSocket, MCP, or the OpenAI-compatible Chat API, including the document surfaces and workflow execution.

AGPL-3.0Auto-check passedBackend & APIs

Install Nodetool API Reference

skills CLI
$ npx skills add nodetool-ai/nodetool --skill nodetool-api-reference -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install nodetool-ai/nodetool nodetool-api-reference --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/system-skills/nodetool-api-reference .claude/skills/nodetool-api-reference && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
nodetool-api-reference
GitHub stars
554
Token cost
~2.8k tokens
SKILL.md length
641 words
Files
1
Skills in repo
130
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Integrate with NodeTool over REST, tRPC, MsgPack WebSocket, MCP, or the OpenAI-compatible Chat API, including the document surfaces and workflow execution.

  • Tasks that involve gRPC and Protobuf
  • SKILL.md covers Workflows, Documents (tRPC), Document REST routes and Collections (RAG), plus 7 more sections
  • Calls curl and npm; needs SUPABASE_KEY and SERVER_AUTH_TOKEN
  • Tasks that involve Realtime and WebSockets

What it does

Nodetool API Reference is an agent skill from nodetool-ai/nodetool. Integrate with NodeTool over REST, tRPC, MsgPack WebSocket, MCP, or the OpenAI-compatible Chat API, including the document surfaces and workflow execution.

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering gRPC and Protobuf and Realtime and WebSockets. It works with tRPC, OpenAI, Model Context Protocol and Supabase. The repository describes itself as: Agent-first Creative Workspace. The licence is AGPL-3.0.

When your agent uses it

  • Tasks that involve gRPC and Protobuf
  • Tasks that involve Realtime and WebSockets

Example prompts

  • “/nodetool-api-reference”

Requirements

  • Python 3
  • A credential in SUPABASE_KEY
  • A credential in SERVER_AUTH_TOKEN

What it can do on your machine

Read from SKILL.md and the folder at commit f99c652. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use curl and npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • SUPABASE_KEY
    • SERVER_AUTH_TOKEN
    • OPENAI_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Nodetool API Reference loads about 2.8k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 641 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~45
When it runs · the whole SKILL.md, loaded when a task matches
~2.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nodetool-ai/nodetool at commit f99c652, republished under its AGPL-3.0 licence (© nodetool-ai). 641 words, ~2,770 tokens.

Download SKILL.mdSave it as .claude/skills/nodetool-api-reference/SKILL.md (or your agent's skills folder).
name
nodetool-api-reference
description
Integrate with NodeTool over REST, tRPC, MsgPack WebSocket, MCP, or the OpenAI-compatible Chat API, including the document surfaces and workflow execution.

You help users integrate with NodeTool's HTTP + WebSocket server (default http://localhost:7777). Start it with nodetool serve (flags: --host, --port).

Surfaces

SurfacePath prefixUse case
REST/api/...Workflows, assets, collections, models, bundles, health
tRPC/trpc/...The document surfaces: timelines, storyboards, sketches, scripts, applications, JS scripts, projects, skills, settings
OpenAI-compatible/v1/...Chat completions + model list
WebSocket/wsRun/cancel/stream jobs, live chat, live editor tools
MCP/mcpAgent tools over streamable HTTP, for Claude Desktop and CLI agents

The server mode (desktop / private / public) and auth are controlled by environment variables (NODETOOL_SERVER_MODE, AUTH_PROVIDER), not CLI flags.

Pick the right surface. REST covers workflows, assets and the portable bundles. Everything that is a document someone edits (a timeline sequence, a storyboard, a sketch, a script, a mini app, a JS script) is a tRPC router, and the REST routes for those kinds cover only import, export and build. An integration that reads or writes a document calls tRPC, or calls the agent capability of the same name over /mcp.

Authentication

Authenticated endpoints use a Bearer token:

Authorization: Bearer <TOKEN>

The server picks its mode from the Supabase credentials:

  • Supabase mode (SUPABASE_URL and SUPABASE_KEY both set): send a Supabase JWT. Every non-public endpoint requires it.
  • Local mode (default): loopback requests need no token and run as user "1". Other sources get 401.

The server does not accept SERVER_AUTH_TOKEN as a bearer token.

REST Endpoints

Workflows

bash
# List workflows
curl http://localhost:7777/api/workflows \
  -H "Authorization: Bearer TOKEN"

# Get a workflow
curl http://localhost:7777/api/workflows/<id> \
  -H "Authorization: Bearer TOKEN"

# Export helpers
curl http://localhost:7777/api/workflows/<id>/dsl-export      # TypeScript DSL
curl http://localhost:7777/api/workflows/<id>/export-bundle   # .nodetool bundle (zip)

Running a workflow is done over WebSocket (/ws, see below), not via a REST /run endpoint. From a terminal you can also run with the CLI: nodetool workflows run <id> --params '{"key":"value"}'.

Documents (tRPC)

The routers under /trpc, one per document kind: timeline, storyboards, sketch, scripts, applications, jsScripts, workflows, projects, assets, collections, jobs, models, nodes, memories, messages, threads, settings, skills, storage, packs, costs, credits, files, fonts, games, integrations, triggers, users, worker, workspace.

Each follows the same shape: list, get, create, update (compare-and-swap on updated_at), delete, plus sub-routers. Whole-document snapshots are timeline.versions, sketch.documentVersions and jsScripts.documentVersions (sketch.versions is a different thing: the per-layer generation takes). applications also carries publish, released, deploy, budget and usage, because publishing an app locks in the current graph of every workflow it runs and caps what it may spend. Read the router in packages/websocket/src/trpc/routers/ for the exact procedure names rather than guessing them. /trpc/healthz answers without auth.

An agent reaches the same data through the capability tools, which need no client: list_timelines, get_storyboard, edit_sketch, save_js_script, edit_app, and so on.

Show full SKILL.md (241 more words)Show less

Document REST routes

The REST side of the document kinds is import, export and build.

bash
# Mini apps
curl http://localhost:7777/api/applications/:id/export-bundle       # app + every bound graph
curl -X POST http://localhost:7777/api/applications/import-bundle
curl -X POST http://localhost:7777/api/applications/build           # {prompt|spec, provider, model, ...}
curl -X POST http://localhost:7777/api/applications/debug
curl http://localhost:7777/api/applications/examples
curl -X POST http://localhost:7777/api/applications/examples/:slug/install

# Timelines and storyboards
curl http://localhost:7777/api/timelines/:id/export-zip
curl -X POST http://localhost:7777/api/timelines/import-zip
curl http://localhost:7777/api/storyboards/:id/export-zip
curl -X POST http://localhost:7777/api/timelines/:id/isolate-subject

# JS scripts
curl -X POST http://localhost:7777/api/js-scripts/:id/run

A build or an interactive debug runs for minutes, so those routes accept poll: true, return a session id, and are read at GET /api/debug/sessions/:id until they settle. Cancel with POST /api/debug/sessions/:id/cancel.

Collections (RAG)

bash
# Index a file into a collection
curl -X POST http://localhost:7777/api/collections/<name>/index \
  -H "Authorization: Bearer TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"file_path": "/path/to/document.pdf"}'

Models

bash
# OpenAI-compatible model list
curl http://localhost:7777/v1/models -H "Authorization: Bearer TOKEN"

Storage / Assets

bash
# Asset bytes are served under /api/storage/...
curl http://localhost:7777/api/storage/<path>

Health

bash
curl http://localhost:7777/health      # liveness (no auth)
curl http://localhost:7777/ready        # readiness
curl http://localhost:7777/api/health   # detailed health

Chat API (OpenAI-Compatible)

HTTP

bash
# Chat completion
curl -X POST http://localhost:7777/v1/chat/completions \
  -H "Authorization: Bearer TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-5.4",
    "messages": [
      {"role": "system", "content": "You are a helpful assistant."},
      {"role": "user", "content": "Hello!"}
    ],
    "stream": false
  }'

# Streaming (Server-Sent Events)
curl -X POST http://localhost:7777/v1/chat/completions \
  -H "Authorization: Bearer TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"model": "gpt-5.4", "messages": [{"role": "user", "content": "Hi"}], "stream": true}'

Python Client (OpenAI SDK)

python
import openai

client = openai.OpenAI(api_key="TOKEN", base_url="http://localhost:7777/v1")

response = client.chat.completions.create(
    model="gpt-5.4",
    messages=[{"role": "user", "content": "Hello!"}],
)
print(response.choices[0].message.content)

# Streaming
stream = client.chat.completions.create(
    model="gpt-5.4",
    messages=[{"role": "user", "content": "Hello!"}],
    stream=True,
)
for chunk in stream:
    if chunk.choices[0].delta.content:
        print(chunk.choices[0].delta.content, end="")

JavaScript Client

typescript
const response = await fetch("http://localhost:7777/v1/chat/completions", {
  method: "POST",
  headers: {
    Authorization: "Bearer TOKEN",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    model: "gpt-5.4",
    messages: [{ role: "user", content: "Hello!" }],
    stream: false,
  }),
});
const data = await response.json();
console.log(data.choices[0].message.content);

WebSocket API — Running Jobs

Endpoint: ws(s)://<host>/ws. Messages are an envelope { command, data }. (In the editor, MsgPack is used; JSON also works for simple clients.)

typescript
const socket = new WebSocket("ws://localhost:7777/ws");

// Start a workflow run
socket.send(JSON.stringify({
  command: "run_job",
  data: {
    type: "run_job_request",
    api_url: "http://localhost:7777/api",
    workflow_id: "<uuid>",
    job_type: "workflow",
    auth_token: "<token>",
    params: { input_name: "value" },
    job_id: "<uuid>",
    user_id: "1",
    execution_strategy: "threaded",
  },
}));

socket.onmessage = (event) => {
  const msg = JSON.parse(event.data);
  switch (msg.type) {
    case "job_update":
      console.log(`Job ${msg.status}`); // running | completed | failed | cancelled | suspended
      if (msg.result) console.log("Result:", msg.result);
      break;
    case "node_update":
      console.log(`Node ${msg.node_name}: ${msg.status}`);
      break;
    case "node_progress":
      console.log(`Progress: ${msg.progress}/${msg.total}`);
      break;
    case "output_update":
      console.log(`Output ${msg.output_name}:`, msg.value);
      break;
    case "chunk":
      process.stdout.write(msg.content);
      break;
    case "log_update":
      console.log(`[${msg.severity}] ${msg.content}`);
      break;
  }
};

Job Control Commands

typescript
socket.send(JSON.stringify({ command: "cancel_job",  data: { job_id: "...", workflow_id: "..." } }));
socket.send(JSON.stringify({ command: "pause_job",   data: { job_id: "...", workflow_id: "..." } }));
socket.send(JSON.stringify({ command: "resume_job",  data: { job_id: "...", workflow_id: "..." } }));

// Stream input into a running node, then close the stream
socket.send(JSON.stringify({ command: "stream_input",     data: { input: "name", value: "data", handle: "..." } }));
socket.send(JSON.stringify({ command: "end_input_stream", data: { input: "name", handle: "..." } }));

Server Message Types

TypeKey fieldsPurpose
job_updatestatus, result, error, costJob lifecycle
node_updatenode_id, node_name, status, error, resultNode lifecycle
node_progressprogress, total, chunkProgress tracking
output_updateoutput_name, value, output_typeNode output values
log_updatecontent, severityLog messages
chunkcontent, doneStreaming text

MCP

/mcp serves the agent capability tools over streamable HTTP, so an outside agent drives NodeTool with the same calls the in-product agent uses. Reach it three ways:

  • nodetool mcp install configures a CLI agent (Claude Code, Codex).
  • In a NodeTool checkout, npm run build:mcpb builds dist/nodetool.mcpb, a one-file bundle Claude Desktop installs by drag-and-drop. It is a stdio-to-HTTP bridge against a running server's /mcp, and it starts in offline mode when the server is down, then hot-attaches when it appears.
  • A deployed server is reached by pointing the client at /mcp with a token minted in Settings → MCP → Connect an agent remotely.

Server Management (CLI)

bash
nodetool serve                        # Start server (default 127.0.0.1:7777)
nodetool serve --host 0.0.0.0          # Bind all interfaces
nodetool serve --port 8080             # Custom port
nodetool workflows list                # List saved workflows
nodetool workflows get <id>            # Get workflow details
nodetool workflows run <id>            # Run a workflow (uses the local DB)
nodetool jobs list                     # List execution jobs
nodetool secrets store OPENAI_API_KEY  # Store an API key

© nodetool-ai, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in packages/system-skills/nodetool-api-reference of nodetool-ai/nodetool.

Open the folder on GitHubat commit f99c652

Compare with similar skills

Nodetool API Reference next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Nodetool API Reference compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nodetool API Reference this skillnodetool-ai/nodetool554—~2.8kAutomated safety check: PassAGPL-3.0
Supabase Development and Debuggingsupabase/agent-skills2.7k3 repos~3.6kAutomated safety check: PassMIT
Spider Kingaoyunyang/spider-king-skill507—~7.3kAutomated safety check: PassMIT
Trpc PatternsFranciscoMoretti/chat-js1.2k—~288Automated safety check: PassApache-2.0
Lazy Prefetch PatternFranciscoMoretti/chat-js1.2k—~217Automated safety check: PassApache-2.0
MCP Integrationhomarr-labs/homarr5k—~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • Official

    General Supabase skill for database, auth, Edge Functions, Realtime and storage work, plus client libraries, migrations, security audits, debugging and reading logs.

    2.7k GitHub starsUsed in 3 repos~3.6k tokens
    Backend & APIsAuto-check passed
  • Spider King

    aoyunyang/spider-king-skill

    Pure-web protocol reverse skill: turn hostile browser clients into browser-free Python collectors.

    507 GitHub stars~7.3k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed
  • Trpc Patterns

    FranciscoMoretti/chat-js

    Implement ChatJS tRPC routers, TanStack Query hooks, mutations, and cache invalidation.

    1.2k GitHub stars~288 tokensUpdated today
    Backend & APIsAuto-check passed
  • Lazy Prefetch Pattern

    FranciscoMoretti/chat-js

    Use the ChatJS React Query v5 lazy-prefetch pattern without blocking server rendering.

    1.2k GitHub stars~217 tokensUpdated today
    Backend & APIsAuto-check passed
  • MCP Integration

    homarr-labs/homarr

    Expose Homarr tRPC procedures safely through MCP. An agent skill from homarr-labs/homarr.

    5k GitHub stars~1.1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Openai Docs

    aafqaq/codex-lb-enhanced

    A skill your agent uses when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations (for example: Codex, Responses API, Chat Completions…

    102 GitHub starsUsed in 3 repos~861 tokens
    DevOps & CloudAuto-check passed

More from nodetool-ai/nodetool

All 130 skills in this repo
  • Beat Sync Editing

    nodetool-ai/nodetool

    Cut a NodeTool timeline to music and shape its pacing — detect the beat grid, place cuts on phrases, pick a cut type, build speed ramps with time remap, and give the piece an arc.

    554 GitHub stars~2.6k tokensUpdated today
    Auto-check passed
  • Caption Titles

    nodetool-ai/nodetool

    Add and animate a consistent text layer on an existing NodeTool timeline.

    554 GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Color Motion

    nodetool-ai/nodetool

    Choose and animate colour on a NodeTool timeline, including shape and text gradients, colour grades, 3D LUTs, and dither.

    554 GitHub stars~2.3k tokensUpdated today
    Auto-check passed
  • Commercial Beat Sheet

    nodetool-ai/nodetool

    Write a shootable, precisely timed commercial beat sheet and store it as a NodeTool storyboard, with a consistent entity roster behind every shot.

    554 GitHub stars~4.6k tokensUpdated today
    Auto-check passed
  • Elevenlabs Audio Prompting

    nodetool-ai/nodetool

    Direct ElevenLabs speech, dialogue, sound effects and music — the bracketed audio tags v3 acts on and why the voice decides whether a tag lands, stability as the delivery dial, punctuation instead…

    554 GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Frame Composition

    nodetool-ai/nodetool

    Stage the frame on a NodeTool timeline — grids, focal placement, safe areas per aspect ratio, depth layers and parallax, camera moves, and where elements enter and leave.

    554 GitHub stars~3.5k tokensUpdated today
    Auto-check passed

Categories

Questions about Nodetool API Reference

What does Nodetool API Reference do?

Integrate with NodeTool over REST, tRPC, MsgPack WebSocket, MCP, or the OpenAI-compatible Chat API, including the document surfaces and workflow execution. Nodetool API Reference is an agent skill from nodetool-ai/nodetool. Integrate with NodeTool over REST, tRPC, MsgPack WebSocket, MCP, or the OpenAI-compatible Chat API, including the document surfaces and workflow execution.

When should I use Nodetool API Reference?

Nodetool API Reference fits situations like: tasks that involve gRPC and Protobuf; tasks that involve Realtime and WebSockets.

How do I install Nodetool API Reference in Claude Code?

Run `npx skills add nodetool-ai/nodetool --skill nodetool-api-reference -a claude-code`. Or copy the skill folder (packages/system-skills/nodetool-api-reference in nodetool-ai/nodetool) into .claude/skills/nodetool-api-reference in your project. Claude Code loads it when a task matches its description.

How do I install Nodetool API Reference in Codex?

Run `npx skills add nodetool-ai/nodetool --skill nodetool-api-reference -a codex`. Or copy the skill folder (packages/system-skills/nodetool-api-reference in nodetool-ai/nodetool) into .agents/skills/nodetool-api-reference in your project. Codex loads it when a task matches its description.

Can I use Nodetool API Reference in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nodetool-ai/nodetool --skill nodetool-api-reference -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nodetool-api-reference, .gemini/skills/nodetool-api-reference, .github/skills/nodetool-api-reference and .opencode/skills/nodetool-api-reference in your project.

What does Nodetool API Reference need to run?

Going by SKILL.md and its folder, Nodetool API Reference needs the command-line tools its instructions call (curl and npm) and credentials named SUPABASE_KEY, SERVER_AUTH_TOKEN and OPENAI_API_KEY. Our summary lists: Python 3; A credential in SUPABASE_KEY; A credential in SERVER_AUTH_TOKEN.

Does Nodetool API Reference access the network?

SKILL.md contains no URLs. Its commands use curl and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Nodetool API Reference safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Nodetool API Reference use?

Nodetool API Reference is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Nodetool API Reference use?

About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Nodetool API Reference?

Skills that share tags, products or a category with Nodetool API Reference: Supabase Development and Debugging (supabase/agent-skills, 2.7k stars), Spider King (aoyunyang/spider-king-skill, 507 stars), Trpc Patterns (FranciscoMoretti/chat-js, 1.2k stars) and Lazy Prefetch Pattern (FranciscoMoretti/chat-js, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nodetool API Reference?

nodetool-ai (a GitHub organization) maintains it in nodetool-ai/nodetool, which has 554 GitHub stars. The repository holds 130 skills in this directory. The repository was last updated on October 7, 2026.

Source: nodetool-ai/nodetool on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.