360 Secure SkillHub
360 安全技能中心

Cronfree

该 Skill 通过 OOMOL 的 oo CLI 连接 Cronfree，先查询动作 schema，再以 JSON 载荷创建或删除按 webhook 地址关联的定时计划。创建为写操作，删除为破坏性操作，均需用户确认；运行依赖 OOMOL 登录与 Cronfree 连接。

oomol
oomol
热度 7.64
最近更新 2026-09-23 18:55:20
分类：自动化依赖：代码执行 / 第三方 API应用场景：日程安排 / 工作流 / API 集成

安装技能

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

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

Cronfree

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

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

oo connector run "cronfree" --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_schedule — Create a recurring Cronfree schedule that sends POST requests to a webhook URL. [write]
  • delete_schedule — Delete the Cronfree schedule associated with a webhook URL. [destructive]

Safety

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

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

Resources