360 Secure SkillHub
360 安全技能中心

SuperSaaS

该 Skill 通过 OOMOL 的 oo CLI 调用 super_saas 连接器，读取 SuperSaaS 账号中的预约、日程、资源、分组、表单、字段名及最近变更等数据，凭据由平台在服务端注入。已列出的动作均为只读操作，需联网执行，并依赖已安装并登录的 oo CLI 与已连接的 SuperSaaS 账号。

oomol
oomol
热度 48.21
最近更新 2026-09-15 12:02:59
分类：自动化依赖：第三方 API / 代码执行应用场景：日程安排 / 工作流

安装技能

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

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

SuperSaaS

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

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

oo connector run "super_saas" --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

  • list_appointments — List appointments or slots for one SuperSaaS schedule in a time range.
  • list_field_names — List available SuperSaaS fields for a schedule or for the user object.
  • list_groups — List groups in the connected SuperSaaS account.
  • list_recent_changes — List recently changed bookings for one SuperSaaS schedule.
  • list_resources — List resources or services for one SuperSaaS schedule.
  • list_schedules — List schedules in the connected SuperSaaS account.
  • list_super_forms — List SuperForms in the connected SuperSaaS account.

Safety

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

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

Resources