360 Secure SkillHub
360 安全技能中心

Apify

核心功能是通过绑定的OOMOL账号操作Apify平台，支持获取用户/actor/运行/数据集信息、启动actor运行等读写操作。典型场景为需操作Apify数据或运行爬虫/自动化任务的场景。输入为符合指定schema的JSON payload，通过oo CLI命令执行；输出为结构化JSON结果，写操作需经用户确认。

oomol
oomol
热度 53.85
最近更新 2026-09-20 11:28:25
分类：自动化依赖：代码执行 / MCP 服务应用场景：自动化脚本 / API 集成 / 数据处理

安装技能

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

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

Apify

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

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

oo connector run "apify" --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_actor — Retrieve metadata for one Apify actor by identifier.
  • get_current_user — Retrieve the currently authenticated Apify user account.
  • get_dataset_items — Retrieve JSON items from one Apify dataset.
  • get_run — Retrieve the current status and storage identifiers for one Apify actor run.
  • run_actor — Start one Apify actor run with an optional JSON input payload. [write]

Safety

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

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

Resources