Agent skill

Sandbox Supabase

Read and write Supabase tables from a Code node or CodeAct action, with NodeTool's PostgREST request builder running on the host

AGPL-3.0Auto-check passedDocuments & Office

Install Sandbox Supabase

skills CLI

$ npx skills add nodetool-ai/nodetool --skill sandbox-supabase -a claude-code

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

GitHub CLI

$ gh skill install nodetool-ai/nodetool sandbox-supabase --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/sandbox-packs/sandbox-supabase .claude/skills/sandbox-supabase && 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/

Paste into Claude Code

Install the "sandbox-supabase" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/sandbox-packs/sandbox-supabase into .claude/skills/sandbox-supabase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sandbox-supabase", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/nodetool-ai/nodetool/tree/main/packages/sandbox-packs/sandbox-supabase

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add nodetool-ai/nodetool --skill sandbox-supabase -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install nodetool-ai/nodetool sandbox-supabase --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/sandbox-packs/sandbox-supabase .agents/skills/sandbox-supabase && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "sandbox-supabase" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/sandbox-packs/sandbox-supabase into .agents/skills/sandbox-supabase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sandbox-supabase", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add nodetool-ai/nodetool --skill sandbox-supabase -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install nodetool-ai/nodetool sandbox-supabase --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/sandbox-packs/sandbox-supabase .cursor/skills/sandbox-supabase && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "sandbox-supabase" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/sandbox-packs/sandbox-supabase into .cursor/skills/sandbox-supabase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sandbox-supabase", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/nodetool-ai/nodetool.git --path packages/sandbox-packs/sandbox-supabase

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add nodetool-ai/nodetool --skill sandbox-supabase -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install nodetool-ai/nodetool sandbox-supabase --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/sandbox-packs/sandbox-supabase .gemini/skills/sandbox-supabase && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "sandbox-supabase" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/sandbox-packs/sandbox-supabase into .gemini/skills/sandbox-supabase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sandbox-supabase", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install nodetool-ai/nodetool sandbox-supabase

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add nodetool-ai/nodetool --skill sandbox-supabase -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/sandbox-packs/sandbox-supabase .github/skills/sandbox-supabase && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "sandbox-supabase" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/sandbox-packs/sandbox-supabase into .github/skills/sandbox-supabase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sandbox-supabase", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add nodetool-ai/nodetool --skill sandbox-supabase -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install nodetool-ai/nodetool sandbox-supabase --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nodetool-ai/nodetool.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/sandbox-packs/sandbox-supabase .opencode/skills/sandbox-supabase && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "sandbox-supabase" agent skill from https://github.com/nodetool-ai/nodetool/tree/main/packages/sandbox-packs/sandbox-supabase into .opencode/skills/sandbox-supabase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sandbox-supabase", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: sandbox-supabase
GitHub stars: 560
Token cost: ~822 tokens
SKILL.md length: 277 words
Files: 2
Skills in repo: 127
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: AGPL-3.0

At a glance

Read and write Supabase tables from a Code node or CodeAct action, with NodeTool's PostgREST request builder running on the host

Documents & Office work in your project
SKILL.md covers from — one table, rpc — a Postgres function and Gotchas
Needs SUPABASE_KEY

What it does

Sandbox Supabase is an agent skill from nodetool-ai/nodetool. Read and write Supabase tables from a Code node or CodeAct action, with NodeTool's PostgREST request builder running on the host

Its SKILL.md is about 820 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `package.json`).

It sits in Documents & Office. It works with Supabase. The repository describes itself as: Agent-first Creative Workspace. The licence is AGPL-3.0.

When your agent uses it

Documents & Office work in your project

Example prompts

“/sandbox-supabase”

Requirements

A credential in SUPABASE_KEY

What it can do on your machine

Read from SKILL.md and the folder at commit 58765d3. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sandbox Supabase loads about 822 tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 277 words of instructions outside code blocks.

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

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 58765d3, republished under its AGPL-3.0 licence (© nodetool-ai). 277 words, ~822 tokens.

Download SKILL.mdSave it as .claude/skills/sandbox-supabase/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: sandbox-supabase
description: Read and write Supabase tables from a Code node or CodeAct action, with NodeTool's PostgREST request builder running on the host

Supabase in the sandbox

Specifier: @nodetool-ai/sandbox-supabase. Import it at the top of the body.

Supabase's REST surface is PostgREST: the whole query lives in the URL and the write semantics live in a Prefer header. Both are easy to get subtly wrong — an upsert without resolution=merge-duplicates is just a failed insert — so this pack does the encoding.

Nothing here sends a request. Both exports build one; the guest's own fetch sends it, under the run's fetch cap and SSRF guard.

from — one table

import { from } from "@nodetool-ai/sandbox-supabase";

const url = await nodetool.secrets.get("SUPABASE_URL");
const key = await nodetool.secrets.get("SUPABASE_KEY");

const req = await from({
  url, key,
  table: "issues",
  select: "id,title,status",
  filters: { status: "eq.open" },
  order: "created_at.desc",
  limit: 20
});
const res = await fetch(req.url, req);
if (!res.ok) throw new Error(`Supabase select failed: ${res.status}`);
return { rows: res.json };

method picks the operation:

method	operation
`GET` (default)	select
`POST`	insert, or upsert with `onConflict`
`PATCH`	update the rows the filters match
`DELETE`	delete the rows the filters match

Options: url and key (required), table (required), method, select, filters, order, limit, offset, body, onConflict, count, returning, query.

Filters take either form:

filters: { status: "eq.open", priority: "in.(high,urgent)" }   // raw PostgREST
filters: { age: { gte: 18, lt: 65 } }                          // operator object

Insert

const req = await from({ url, key, table: "events", method: "POST", body: inputs.rows });

Update the matching rows

const req = await from({
  url, key, table: "issues", method: "PATCH",
  filters: { id: `eq.${inputs.id}` },
  body: { status: "closed" }
});

Upsert — onConflict names the unique column and turns the insert into a merge:

const req = await from({
  url, key, table: "users", method: "POST",
  onConflict: "email", body: inputs.users
});

A write returns the affected rows. Pass returning: "minimal" when you do not want them back.

rpc — a Postgres function

import { rpc } from "@nodetool-ai/sandbox-supabase";

const req = await rpc({ url, key, fn: "search_issues", args: { term: inputs.term } });
return { rows: (await fetch(req.url, req)).json };

Gotchas

Every export is async. A host call is a round trip.
A DELETE or PATCH with no filters hits every row. PostgREST does not refuse it. Pass the filters.
The anon key obeys row-level security. A select that returns [] against a table with rows usually means RLS, not an empty table. The service-role key bypasses it — and bypasses it for every row, so keep it out of anything a user's prompt can steer.
Errors arrive as JSON with a non-2xx status. Check res.ok and read res.json.message; PostgREST says exactly what it disliked.
Supabase caps a page at 1000 rows. Page with limit and offset.

Files

SKILL.md and 1 other file in packages/sandbox-packs/sandbox-supabase of nodetool-ai/nodetool.

SKILL.md
package.json

Open the folder on GitHubat commit 58765d3

Compare with similar skills

Sandbox Supabase 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.

Sandbox Supabase compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Sandbox Supabase this skillnodetool-ai/nodetool	560	—	~822	Automated safety check: Pass	AGPL-3.0	today
Review The Docssupabase/supabase	111k	—	~4.6k	Automated safety check: Pass	Apache-2.0	today
Linkedin Outreachgooseworks-ai/goose-skills	1.2k	1 repos	~4.4k	Automated safety check: Notes	MIT	yesterday
Sft Cleanup Hf Onlyopen-thoughts/OpenThoughts-Agent	301	—	~1.1k	Automated safety check: Pass	Apache-2.0	11 days ago
Ask The Docssupabase/supabase	111k	—	~2.4k	Automated safety check: Pass	Apache-2.0	today
Data Exportindranilbanerjee/digital-marketing-pro	859	1 repos	~3.7k	Automated safety check: Pass	MIT	6 days ago

Similar skills

Review The Docs
supabase/supabase
Official
Review Supabase docs changes locally in your supabase/supabase checkout — either an open PR (triage, classify, verify) or your own branch before opening a PR (local self-review).
111k GitHub stars~4.6k tokensUpdated today
Documents & OfficeAuto-check passed
Linkedin Outreach
gooseworks-ai/goose-skills
End-to-end LinkedIn outreach campaign builder. An agent skill from gooseworks-ai/goose-skills.
1.2k GitHub starsUsed in 1 repo~4.4k tokens
Documents & OfficeAuto-check: notes
Sft Cleanup Hf Only
open-thoughts/OpenThoughts-Agent
Clean up a completed NON-AGENTIC / HF-only SFT model — HF upload WITHOUT Supabase DB registration.
301 GitHub stars~1.1k tokensUpdated 11 days ago
Documents & OfficeAuto-check passed
Ask The Docs
supabase/supabase
Official
Answer questions about the Supabase docs app (apps/docs) using documented architecture, build pipeline, and review-pattern notes, and apply feature-design principles (codebase reuse, coding…
111k GitHub stars~2.4k tokensUpdated today
Documents & OfficeAuto-check passed
Data Export
indranilbanerjee/digital-marketing-pro
Export marketing data — metrics, contacts, campaigns, performance snapshots — to BigQuery, Google Sheets, or Supabase as clean tabular data with schema documentation, PII redaction, and post-export…
859 GitHub starsUsed in 1 repo~3.7k tokens
Documents & OfficeAuto-check passed
Take Doc Screenshots
pgplex/pgconsole
Take screenshots of the running pgconsole app for documentation.
155 GitHub stars~841 tokensUpdated 1 mo ago
DatabasesAuto-check passed

More from nodetool-ai/nodetool

All 127 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.
560 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.
560 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.
560 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.
560 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…
560 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.
560 GitHub stars~3.5k tokensUpdated today
Auto-check passed

Works with

Supabase

Questions about Sandbox Supabase

What does Sandbox Supabase do?

Read and write Supabase tables from a Code node or CodeAct action, with NodeTool's PostgREST request builder running on the host. Sandbox Supabase is an agent skill from nodetool-ai/nodetool.

When should I use Sandbox Supabase?

Sandbox Supabase fits situations like: documents & Office work in your project.

How do I install Sandbox Supabase in Claude Code?

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

How do I install Sandbox Supabase in Codex?

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

Can I use Sandbox Supabase 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 sandbox-supabase -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sandbox-supabase, .gemini/skills/sandbox-supabase, .github/skills/sandbox-supabase and .opencode/skills/sandbox-supabase in your project.

What does Sandbox Supabase need to run?

Going by SKILL.md and its folder, Sandbox Supabase needs credentials named SUPABASE_KEY. Our summary lists: A credential in SUPABASE_KEY.

Does Sandbox Supabase access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Sandbox Supabase 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 Sandbox Supabase use?

Sandbox Supabase 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 Sandbox Supabase use?

About 822 tokens (SKILL.md is roughly 3.3k 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 Sandbox Supabase?

Skills that share tags, products or a category with Sandbox Supabase: Review The Docs (supabase/supabase, 111k stars), Linkedin Outreach (gooseworks-ai/goose-skills, 1.2k stars), Sft Cleanup Hf Only (open-thoughts/OpenThoughts-Agent, 301 stars) and Ask The Docs (supabase/supabase, 111k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sandbox Supabase?

nodetool-ai (a GitHub organization) maintains it in nodetool-ai/nodetool, which has 560 GitHub stars. The repository holds 127 skills in this directory. The repository was last updated on October 9, 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.

Install Sandbox Supabase

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Supabase in the sandbox

from — one table

rpc — a Postgres function

Gotchas

Files

Compare with similar skills

Similar skills

More from nodetool-ai/nodetool

Related

Questions about Sandbox Supabase