360 Secure SkillHub
360 安全技能中心

Browserless

核心功能为调用Browserless执行三类操作：抓取渲染后的网页HTML内容、生成并返回base64格式的PDF文件、生成并返回base64格式的网页截图。通过oo CLI执行，OOMOL后台注入凭据，无需用户处理令牌。典型场景包括网页数据爬取、网页存档等。输入需符合对应动作的JSON schema，输出为含执行结果与ID的JSON结构，仅在命令出错时需执行首次安装、登录或连接步骤。

oomol
oomol
热度 53.98
最近更新 2026-09-15 13:09:07
分类：自动化依赖：代码执行 / MCP 服务应用场景：自动化脚本 / 数据处理 / 文件转换 / 图像生成

安装技能

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

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

Browserless

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

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

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

  • fetch_content — Fetch fully rendered HTML content from Browserless.
  • generate_pdf — Generate a Browserless PDF file and return it as base64 content.
  • take_screenshot — Generate a Browserless screenshot and return it as base64 content.

Safety

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

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

Resources