SkillHub

openclaw-feishu-workspace

v0.1.0

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.

Sourced from ClawHub, Authored by ClawMaster

Installation

Please help me install the skill `openclaw-feishu-workspace` from SkillHub official store. npx skills add xiaonizhou-crypto/openclaw-feishu-workspace

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:
  2. doc
  3. wiki
  4. bitable

  5. Prefer structured, useful outputs over raw dumps.

  6. For docs:

  7. use short sections
  8. use bullets where appropriate
  9. make outputs immediately readable by humans

  10. For wiki:

  11. search before drafting when internal context matters
  12. summarize findings clearly
  13. cite page titles or locations when useful

  14. For bitable:

  15. inspect table metadata and fields before writing when a URL is provided
  16. map values carefully into the right columns
  17. 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