360 Secure SkillHub
360 安全技能中心

ShipStation

该 Skill 通过 oo CLI 调用 OOMOL 的 ship_station 连接器，读取 ShipStation V2 的采购订单与库存数据，提供查询单个采购订单、列出采购订单、列出库存水平和库存仓库四个只读动作；凭据由 OOMOL 服务端注入，用户无需处理原始 token。

oomol
oomol
热度 44.66
最近更新 2026-09-20 11:30:58
分类：数据依赖：代码执行 / 第三方 API应用场景：API 集成 / 数据处理

安装技能

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

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

ShipStation

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

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

oo connector run "ship_station" --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_purchase_order — Retrieve a ShipStation V2 purchase order by ID, including detailed product lines when returned.
  • list_inventory_levels — List ShipStation V2 inventory stock levels and inventory-related properties for SKUs.
  • list_inventory_warehouses — List inventory warehouses configured in ShipStation V2.
  • list_purchase_orders — List ShipStation V2 purchase orders with optional filters and pagination.

Safety

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

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

Resources