360 Secure SkillHub
360 安全技能中心

Podscribe

该 Skill 通过 oo CLI 调用 OOMOL 侧的 podscribe 连接器，提供三个只读动作：查询集成健康状态（可选按广告主与像素过滤）、按 iTunes/YouTube 标识获取节目信息、按查询串与时间范围/媒体类型搜索剧集；执行前先用 schema 命令获取输入输出契约，凭据由服务端注入。

oomol
oomol
热度 43.52
最近更新 2026-09-15 13:17:14
分类：搜索依赖：代码执行 / 第三方 API应用场景：API 集成 / 研究 / 市场分析

安装技能

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

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

Podscribe

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

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

oo connector run "podscribe" --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_integration_health — Retrieve Podscribe integration health, optionally filtered by advertiser and including pixel data.
  • get_show_info — Retrieve Podscribe show information by iTunes or YouTube identifier.
  • search_episodes — Search Podscribe episodes by query string with optional time frame, media type, and show filters.

Safety

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

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

Resources