360 Secure SkillHub
360 安全技能中心

Feishu Workspace

该 Skill 面向飞书(Feishu/Lark)文档、Wiki 与多维表格协作场景,覆盖编写或更新文档、检索 Wiki 内部知识、创建与更新多维表格记录、把对话整理为结构化团队产物,并给出先识别目标载体、结构化输出、写表前先看字段及失败原因说明等流程指引;不含具体接口实现、鉴权配置与数据模板。

xiaonizhou-crypto
xiaonizhou-crypto
热度 59.45
最近更新 2026-05-11 17:31:34
分类:协作依赖:第三方 API应用场景:会议纪要 / 任务管理 / 笔记整理 / 工作流 ...

安装技能

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

执行命令安装此 skill: npx secure-skills-cli add openclaw-feishu-workspace
Metadata
name
Feishu Workspace
description
Use when the user wants to work with Feishu Docs, Wiki, or Bitable for practical team workflows such as meeting notes, knowledge lookup, and project tracking.

Feishu Workspace

Use this skill when a request involves Feishu/Lark content or workflows.

Primary areas

  • Feishu Docs
  • Feishu Wiki
  • Feishu Bitable

Use this skill for

  • writing or updating Feishu docs
  • searching wiki knowledge before answering or drafting
  • creating and updating Bitable records
  • turning conversations into structured team artifacts
  • supporting lightweight PM and ops workflows in Feishu

Preferred workflow

  1. First identify the target surface:

    • doc
    • wiki
    • bitable
  2. Prefer structured, useful outputs over raw dumps.

  3. For docs:

    • use short sections
    • use bullets where appropriate
    • make outputs immediately readable by humans
  4. For wiki:

    • search before drafting when internal context matters
    • summarize findings clearly
    • cite page titles or locations when useful
  5. For bitable:

    • inspect table metadata and fields before writing when a URL is provided
    • map values carefully into the right columns
    • prefer fewer, more structured writes

Output style

When generating Feishu content:

  • concise
  • clean
  • structured
  • useful to a real teammate

Avoid:

  • long fluff
  • vague summaries
  • unstructured walls of text

High-value workflows

  • meeting notes → doc
  • internal knowledge lookup → summary
  • action items → bitable
  • standup updates → project doc
  • planning discussion → structured brief

Failure handling

If an operation fails, explain the likely cause clearly:

  • missing app scope
  • missing file/document access
  • unsupported target type
  • invalid URL/token/table selection

Not for

  • unrelated non-Feishu requests
  • giant migrations unless the user explicitly wants a staged plan
  • blind table writes without understanding the fields