360 Secure SkillHub
360 安全技能中心

Knack

该 Skill 通过 OOMOL 的 oo CLI 调用 knack connector，对 Knack 对象记录执行查询、创建、更新和删除；先读取动作 schema，再以 JSON 载荷运行。写操作需先与用户确认，删除属破坏性操作需显式批准。凭据由 OOMOL 服务端注入，首次使用需安装 CLI、登录并完成连接。

oomol
oomol
热度 51.40
最近更新 2026-09-15 12:33:34
分类：数据依赖：代码执行 / 第三方 API应用场景：数据处理 / API 集成

安装技能

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

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

Knack

Operate Knack through your OOMOL-connected account. This skill calls the knack 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 Knack. 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 "knack" --action "<action_name>"

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

oo connector run "knack" --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_record — Create one Knack record in the selected object with a raw JSON record payload. [write]
  • delete_record — Delete one Knack record by object key and record ID. [destructive]
  • get_record — Retrieve one Knack record by object key and record ID.
  • list_records — List records from one Knack object with optional pagination, sorting, formatting, and filter query parameters.
  • update_record — Update one Knack record by sending a partial JSON payload for the selected object and record ID. [write]

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change Knack 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 — Knack 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=knack

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

Resources