Feishu At Mention

v0.0.2

飞书消息@提及功能。当需要在飞书消息中@群成员时使用此技能。支持三种消息类型:(1) 普通文本消息使用 at user_id 标签格式;(2) 富文本消息使用 JSON 对象格式的 tag at 元素;(3) 卡片消息使用 at id 标签格式。根据消息类型选择正确的@标签格式,确保触发飞书的@通知效果。

1· 379·1 current·1 all-time
byvision qiu@vision-qiu

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for vision-qiu/feishu-at-mention.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Feishu At Mention" (vision-qiu/feishu-at-mention) from ClawHub.
Skill page: https://clawhub.ai/vision-qiu/feishu-at-mention
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Canonical install target

openclaw skills install vision-qiu/feishu-at-mention

ClawHub CLI

Package manager switcher

npx clawhub@latest install feishu-at-mention
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description match the content: SKILL.md provides templates and examples for Feishu @-mentions across text, post (rich text), and interactive (card) messages. The guidance is narrowly scoped to formatting and is appropriate for the stated purpose. Note: the README shows a sample CLI call (feishu_chat action=members) which is not declared as a required binary — that example is informative but not a required dependency of the skill itself.
Instruction Scope
Instructions only show message payload formats, how to obtain open_id from conversation metadata or via an API/CLI example, and list permissions caveats. The instructions do not ask the agent to read arbitrary files, exfiltrate data, or call unknown external endpoints. They do reference retrieving sender_id/open_id from conversation metadata, which is reasonable for a messaging helper but depends on the surrounding agent/tool privileges.
Install Mechanism
No install spec or code files are present. This is the lowest-risk format — nothing is written to disk or executed by the skill itself.
Credentials
The skill declares no required environment variables or credentials, which is consistent because it only provides formatting examples. If you intend to actually call Feishu APIs or the referenced feishu_chat CLI, those integrations will require Feishu credentials (app/bot tokens) configured elsewhere — the skill does not request or manage those secrets.
Persistence & Privilege
always is false and the skill is user-invocable. It does not request persistent or elevated agent privileges and does not attempt to modify other skills or system configuration.
Assessment
This skill is a reference for how to format Feishu @-mentions and is safe to read/install as-is. If you plan to use it to send messages, ensure your agent or environment already has the appropriate Feishu credentials/tools configured (the SKILL.md shows a feishu_chat example but the skill doesn't provide that tool or request its credentials). Also note @all and admin permission requirements in group chats — verify the bot/user has the needed permissions before relying on these templates.

Like a lobster shell, security has layers — review code before you run it.

latestvk97dtj2zftx5fz0vkry9c1pxq182k5kx
379downloads
1stars
2versions
Updated 1mo ago
v0.0.2
MIT-0

飞书消息 @ 提及

根据飞书消息类型选择正确的@标签格式。

1. 普通文本消息(text)

@指定用户

<at user_id="ou_xxxxxxxx">用户名</at>

@所有人

<at user_id="all"></at>

示例

{
  "content": "{\"text\":\"<at user_id=\\\"ou_xxxxxxxx\\\">Tom</at> 请查看此消息\"}"
}

2. 富文本消息(post)

@指定用户

在 content 数组中添加:

{"tag": "at", "user_id": "ou_xxxxxx", "user_name": "Tom"}

@所有人

{"tag": "at", "user_id": "all"}

示例

{
  "zh_cn": {
    "content": [
      [
        {"tag": "text", "text": "通知:"},
        {"tag": "at", "user_id": "ou_xxxxxx", "user_name": "Tom"}
      ]
    ]
  }
}

3. 飞书卡片(interactive)

@指定用户

在卡片 Markdown 内容中使用:

<at id=ou_xxxxxx></at>

@所有人

<at id=all></at>

示例

{
  "elements": [
    {
      "tag": "div",
      "text": {
        "content": "请<at id=ou_xxxxxx></at>处理任务",
        "tag": "lark_md"
      }
    }
  ]
}

格式对比

消息类型@指定用户@所有人关键点
普通文本<at user_id="ou_xxx">名字</at><at user_id="all"></at>需要 user_id 和用户名
富文本{"tag":"at","user_id":"ou_xxx","user_name":"名字"}{"tag":"at","user_id":"all"}JSON 对象格式
卡片<at id=ou_xxx></at><at id=all></at>使用 id(无引号),自闭合

获取 open_id

从对话元数据获取:

  • sender_id: 发送者的 open_id(格式:ou_xxxxxxxx

或通过 API 获取:

feishu_chat action=members chat_id=<群聊 ID> member_id_type="open_id"

注意事项

  1. 权限限制:自定义机器人仅支持使用 open_id@指定人,自建应用可使用 user_id、email 等
  2. @所有人限制:需群组开启相关权限,且机器人需为群主或管理员
  3. 格式严格:不同消息类型的@标签格式不可混用
  4. open_id 格式:以 ou_ 开头

常见错误

❌ 在普通文本中使用卡片格式:

{"content": "{\"text\":\"<at id=ou_xxx></at> 你好\"}"}

❌ 在卡片中使用普通文本格式:

{"content": "请<at user_id=\"ou_xxx\">Tom</at>处理", "tag": "lark_md"}

❌ 富文本中使用错误的属性名:

{"tag": "at", "id": "ou_xxx"}  // 应该是 user_id

Comments

Loading comments...