360 Secure SkillHub
360 安全技能中心

Luma

该 Skill 通过 OOMOL 的 oo CLI 调用 luma 连接器，提供获取日历、活动、活动嘉宾和当前用户资料等只读动作；执行前可先查看动作的输入输出契约，凭据由 OOMOL 服务端注入，用户无需处理原始令牌。列出的动作均为读取类，未定义写入或删除动作。

oomol
oomol
热度 34.51
最近更新 2026-09-15 13:02:58
分类：搜索依赖：代码执行 / 第三方 API应用场景：研究

安装技能

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

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

Luma

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

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

oo connector run "luma" --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_calendar — Get the Luma calendar scoped to the current API key.
  • get_event — Get full details for a Luma event the API key can manage.
  • get_event_guest — Get detailed information for a Luma event guest.
  • get_self — Get the Luma user profile for the current API key.
  • list_calendar_events — List events for the Luma calendar scoped to the current API key.
  • list_event_guests — List registered or invited guests for a Luma event.

Safety

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

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

Resources