Baserow

v0.1.0

Baserow: Create, read, update, and delete rows, list tables and fields. Use when the user wants to interact with Baserow — querying data, creating or updatin...

0· 252·0 current·0 all-time
byJamil Zakirov@jzakirov
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the runtime instructions. Requiring the baserow CLI binary plus BASEROW_TOKEN and BASEROW_URL is appropriate for a Baserow CLI integration.
Instruction Scope
SKILL.md only tells the agent to run the baserow CLI, use the config at ~/.config/baserow-cli/config.toml, and supply service-specific env vars or flags. It does not instruct reading unrelated files or exfiltrating data. Note: the manifest lists no required config paths while the SKILL.md documents a config file location (~/.config/baserow-cli/config.toml); this is an informational mismatch but not a functional concern.
Install Mechanism
No install spec is embedded (instruction-only). The doc suggests installing via 'uv tool install baserow-cli' or 'pip install baserow-cli' — standard but outside the skill's control. If you plan to install, prefer official releases (PyPI or the project's site) and verify package authenticity.
Credentials
Requested env vars (BASEROW_TOKEN, BASEROW_URL) are service-specific and proportional. No unrelated credentials or broad secrets are requested.
Persistence & Privilege
always:false and no special persistence or cross-skill config modifications are requested. The skill does note that destructive commands require '--yes' in non-TTY (agent) contexts — this affects how an agent might run destructive operations and is a normal capability for a CLI wrapper.
Assessment
This skill appears to do what it says: it drives the Baserow CLI and needs your Baserow API token and base URL. Before installing or using it: (1) ensure the 'baserow' CLI you install comes from a trusted source (official project or PyPI) and verify package integrity; (2) limit the BASEROW_TOKEN to the minimum permissions needed and avoid sharing broader credentials; (3) be cautious with destructive commands (delete / batch-delete) — SKILL.md notes non-TTY contexts may accept '--yes', so always confirm intended deletes before running and avoid giving the agent blanket permission to pass --yes; (4) be aware the skill references a config file (~/.config/baserow-cli/config.toml) which may contain tokens or defaults — review its contents and placement; and (5) if you want tighter safety, run the CLI in an environment with limited network access or use a scoped token.

Like a lobster shell, security has layers — review code before you run it.

Plugin bundle (nix)
Skill pack · CLI binary · Config
SKILL.mdCLIConfig
CLI help (from plugin)
baserow --help

Runtime requirements

🗄️ Clawdis
Binsbaserow
EnvBASEROW_TOKEN, BASEROW_URL
latestvk977rtpf4cfwfrhcy50paam12s82b0fw
252downloads
0stars
1versions
Updated 1mo ago
v0.1.0
MIT-0

Baserow CLI

CLI for Baserow — the open-source Airtable alternative. Output is JSON by default — pipe to jq or consume directly.

Setup

uv tool install baserow-cli   # or: pip install baserow-cli
baserow config init            # interactive setup wizard

Config: ~/.config/baserow-cli/config.toml. All values can be set via env vars (BASEROW_TOKEN, BASEROW_URL, BASEROW_TABLE) or CLI flags.

Command Discovery

Do not guess command names or options. Use --help:

baserow --help
baserow rows --help
baserow rows list --help

Quick Reference

ResourceKey commands
baserow tableslist, get <table-id>
baserow fieldslist --table <id>
baserow rowslist, get, create, update, delete
baserow rows batch-*batch-create, batch-update, batch-delete
baserow configinit, show, set

Common Workflows

Discover table structure:

baserow tables list
baserow tables get 42
baserow fields list --table 42

List and search rows:

baserow rows list --table 42
baserow rows list --table 42 --search "quarterly" --size 50
baserow rows list --table 42 --filter "Status__equal=Done" --order-by "-Created"

Create a row:

baserow rows create --table 42 --json '{"Name": "New item", "Status": "Todo"}'

Update a row:

baserow rows update 1 --table 42 --json '{"Status": "Done"}'

Batch operations:

baserow rows batch-create --table 42 --json '[{"Name": "A"}, {"Name": "B"}]'
baserow rows batch-update --table 42 --json '[{"id": 1, "Status": "Done"}, {"id": 2, "Status": "Done"}]'
baserow rows batch-delete --table 42 --json '[3, 4, 5]' --yes

Pipe JSON from stdin:

cat data.json | baserow rows batch-create --table 42 --json -

Important Conventions

  • --table is optional when defaults.table is configured
  • --database is optional when defaults.database is configured
  • Destructive commands (delete, batch-delete) require --yes in non-TTY (agent) contexts
  • --json accepts - to read from stdin
  • Pagination via --page and --size (max 200 per page); default is page 1
  • Errors go to stderr as JSON: {"error": {"type": "...", "message": "...", "status_code": N}}
  • Exit codes: 0 success, 1 error, 2 rate-limited (retry safe)
  • Field values in --json use field names (not IDs)

[!CAUTION] delete and batch-delete commands are destructive — always confirm with the user before executing.

Comments

Loading comments...