360 Secure SkillHub
360 安全技能中心

ParseHub

该 Skill 通过 OOMOL 的 oo CLI 调用 parsehub 连接器，提供 list_projects 与 get_project 两个只读 action，用于列出 API key 可访问的 ParseHub 项目，或按项目 token 获取单个项目。凭据由 OOMOL 服务端注入；首次使用需安装 oo CLI、登录并连接 ParseHub。

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

安装技能

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

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

ParseHub

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

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

oo connector run "parsehub" --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_project — Get one ParseHub project by project token from the API key's accessible project list.
  • list_projects — List ParseHub projects accessible to the API key with optional offset pagination.

Safety

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

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

Resources