360 Secure SkillHub
360 安全技能中心

IP2Proxy

该 Skill 借助 OOMOL 的 oo CLI 调用 ip2proxy 连接器，只提供 lookup_ip 操作：检测单个 IPv4 或 IPv6 地址是否为代理，并返回 IP2Proxy 查询结果。凭据由 OOMOL 服务端注入，用户需预先安装并登录 oo CLI、连接 IP2Proxy；命令因鉴权或连接失败时按一次性设置说明处理。

oomol
oomol
热度 50.13
最近更新 2026-09-15 13:12:59
分类：安全依赖：代码执行 / 第三方 API应用场景：API 集成 / 数据处理

安装技能

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

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

IP2Proxy

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

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

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

  • lookup_ip — Detect whether one IPv4 or IPv6 address is a proxy and return the official IP2Proxy lookup payload.

Safety

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

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

Resources