360 Secure SkillHub
360 安全技能中心

Baserow

该 Skill 通过 oo CLI 的 baserow 连接器操作 Baserow：可列举表与字段、按条件读取行，以及创建、更新、删除行。运行前用 oo connector schema 获取输入输出结构；凭据由 OOMOL 服务端注入，用户不直接管理 token。标记为写入或删除的动作需先向用户确认。

oomol
oomol
热度 50.91
最近更新 2026-09-15 13:09:07
分类：数据依赖：第三方 API / 代码执行应用场景：数据处理 / 工作流

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add oo-baserow
Metadata
name
oo-baserow
description
Baserow (baserow.io). Use this skill for ANY Baserow request — reading, creating, updating, and deleting data. Whenever a task involves Baserow, use this skill instead of calling the API directly.
allowed-tools
["Bash(oo *)"]
metadata
{"title":"Baserow","author":"OOMOL","version":"1.0.3","services":["baserow"],"icon":"https://static.oomol.com/logo/third-party/baserow.svg"}

Baserow

Operate Baserow through your OOMOL-connected account. This skill calls the baserow connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Baserow. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "baserow" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "baserow" --action "<action_name>" --data '<json>' --json
  • --data takes a JSON object string or @path/to/file.json; omit it to send {}.
  • The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

  • create_table_row — Create one row in a Baserow table. [write]
  • delete_table_row — Delete one Baserow row by row ID. [destructive]
  • get_table_row — Read one Baserow row by table ID and row ID.
  • list_table_fields — List the field definitions for one Baserow table.
  • list_table_rows — List rows from one Baserow table with optional search, ordering, filters, and pagination.
  • list_tables — List the Baserow tables accessible to the authenticated database token.
  • update_table_row — Update one existing Baserow row. [write]

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change Baserow state — confirm the exact payload and effect with the user before running.
  • Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

  • oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

    curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux

    irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell

  • Not signed in / authentication error — sign in to your OOMOL account once:

    oo auth login

  • scope_missing / credential_expired / app_not_ready / app_not_found — Baserow is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

    https://console.oomol.com/app-connections?provider=baserow

  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources