360 Secure SkillHub
360 安全技能中心

WaiverFile

面向 WaiverFile 的 OOMOL 连接器 Skill：通过 oo CLI 以只读方式查询站点详情、有效免责声明表单、已签署免责声明（按标识或外部参考号）以及指定时间范围内的即将举行活动。调用前用 oo connector schema 获取动作的输入输出契约，凭据由 OOMOL 服务端注入，用户不直接处理令牌。

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

安装技能

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

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

WaiverFile

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

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

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

  • get_site_details — Get details for the connected WaiverFile site.
  • get_waiver — Get one signed WaiverFile waiver by its identifier.
  • list_upcoming_events — List upcoming WaiverFile events within a UTC date range.
  • list_waiver_forms — List active waiver forms for the connected WaiverFile site.
  • list_waivers_by_reference — List WaiverFile waivers matching one or more external reference identifiers.
  • search_waivers — Search signed WaiverFile waivers by text.

Safety

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

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

Resources