360 Secure SkillHub
360 安全技能中心

Feishu Custom Bot

面向飞书自定义机器人的消息发送 Skill：借助 oo CLI 调用 feishu_custom_bot connector，支持发送文本、富文本、图片、互动卡片和群分享卡片五类消息；各 action 的输入字段需在运行时用 schema 命令查询，凭据由服务端注入，写操作前需与用户确认。

oomol
oomol
热度 51.22
最近更新 2026-09-15 12:43:39
分类：协作依赖：代码执行 / 第三方 API应用场景：工作流 / 自动化脚本

安装技能

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

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

Feishu Custom Bot

Operate Feishu Custom Bot through your OOMOL-connected account. This skill calls the feishu_custom_bot 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 Feishu Custom Bot. 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 "feishu_custom_bot" --action "<action_name>"

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

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

  • send_image_message — Send an image message through the Feishu/Lark custom bot webhook. [write]
  • send_interactive_message — Send an interactive card message through the Feishu/Lark custom bot webhook. [write]
  • send_post_message — Send a post rich-text message through the Feishu/Lark custom bot webhook. [write]
  • send_share_chat_message — Send a shared-chat card through the Feishu/Lark custom bot webhook. [write]
  • send_text_message — Send a text message through the Feishu/Lark custom bot webhook. [write]

Safety

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

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

Resources