360 Secure SkillHub
360 安全技能中心

Deck.co

该 Skill 借助 OOMOL 的 oo CLI 调用 deck_co 连接器操作 Deck.co：创建网站来源、按 ID 查询来源与代理、分页列出代理和来源、验证密钥可用性。凭据由 OOMOL 服务端注入，写操作需先与用户确认；调用前先用 oo connector schema 获取权威输入结构，仅在命令缺失或认证失败时执行一次性安装、登录与连接。

oomol
oomol
热度 41.62
最近更新 2026-09-15 13:10:36
分类：自动化依赖：代码执行 / 第三方 API应用场景：API 集成 / 工作流 / 任务管理

安装技能

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

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

Deck.co

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

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

oo connector run "deck_co" --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_source — Create a Deck.co website source from a URL and optional display name. [write]
  • get_agent — Retrieve a Deck.co agent by ID, including its task summaries.
  • get_source — Retrieve a Deck.co source by ID.
  • list_agents — List Deck.co agents with cursor pagination.
  • list_sources — List Deck.co sources with cursor pagination.
  • test_api_key — Verify that a Deck.co secret key can authenticate with the v2 API.

Safety

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

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

Resources