360 Secure SkillHub
360 安全技能中心

FFHub

该 Skill 通过 OOMOL 的 oo CLI 调用 ffhub 连接器代为操作 FFHub：先读取动作的输入输出 Schema，再以 JSON 载荷执行 create_ffmpeg_task、get_ffmpeg_task 和 list_ffmpeg_tasks，完成 FFmpeg 转码任务的创建、状态查询与列表查看。凭据由服务端注入，写操作需先与用户确认。

oomol
oomol
热度 51.19
最近更新 2026-09-15 13:34:06
分类：自动化依赖：代码执行 / 第三方 API / 读写文件应用场景：视频编辑 / 文件转换 / 工作流 / 自动化脚本

安装技能

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

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

FFHub

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

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

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

  • create_ffmpeg_task — Create a new FFHub FFmpeg transcoding task from a full FFmpeg command or argument-only command string. [write]
  • get_ffmpeg_task — Get the current status, timing, error, and output files for one FFHub FFmpeg task.
  • list_ffmpeg_tasks — List FFHub FFmpeg tasks with optional customer, status, limit, and offset filters.

Safety

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

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

Resources