360 Secure SkillHub
360 安全技能中心

Kernel

该 Skill 借助 OOMOL 的 oo CLI 以连接器方式调用 Kernel 服务，管理浏览器会话的创建、列表查询、详情获取、元数据更新与删除。执行前先读取 action 的输入输出 schema，再以 JSON 载荷运行；凭据由平台服务端注入。写操作需确认载荷，删除操作需明确授权。

oomol
oomol
热度 41.41
最近更新 2026-09-15 12:11:53
分类：自动化依赖：代码执行 / 第三方 API应用场景：API 集成 / 自动化脚本

安装技能

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

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

Kernel

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

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

oo connector run "kernel" --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_browser_session — Create a Kernel browser session and return its connection URLs and metadata. [write]
  • delete_browser_session — Delete a Kernel browser session by session ID or name. [destructive]
  • get_browser_session — Get one Kernel browser session by session ID or name.
  • list_browser_sessions — List Kernel browser sessions with pagination, search, status, and tag filters.
  • update_browser_session — Update mutable Kernel browser session metadata and settings. [write]

Safety

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

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

Resources