360 Secure SkillHub
360 安全技能中心

BrowserStack

通过 OOMOL 的 oo CLI 调用 browserstack 连接器,执行 BrowserStack Automate 的构建与会话查询,以及把会话标记为通过或失败的写入操作;凭证由服务端注入,使用前需安装 CLI、登录并连接 BrowserStack。

oomol
oomol
热度 40.66
最近更新 2026-09-15 13:20:53
分类：开发依赖：代码执行 / 第三方 API应用场景：API 集成 / DevOps / 数据处理

安装技能

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

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

BrowserStack

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

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

oo connector run "browserstack" --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_session — Retrieve details for a BrowserStack Automate session.
  • list_build_sessions — List BrowserStack Automate sessions for a build.
  • list_builds — List recent BrowserStack Automate builds with optional status, project, and pagination filters.
  • update_session_status — Mark a BrowserStack Automate session as passed or failed with a reason. [write]

Safety

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

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

Resources