OpenParable
Skip to content
← Back to skills

Feishu

Apps & Automation
feishu

Feishu is an Agent Skill for apps & automation published in the Hmbown/CodeWhale repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Hmbown/CodeWhale/blob/HEAD/crates/tui/assets/skills/feishu/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/feishu, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Feishu / Lark

Use this skill when the user asks for Feishu, Lark, or "飞书" integration work.

Ground Rules

  • Feishu China APIs use open.feishu.cn; Lark international APIs use open.larksuite.com.
  • Never hardcode app secrets, webhook secrets, tenant tokens, or user tokens. Use environment variables such as FEISHU_APP_ID, FEISHU_APP_SECRET, FEISHU_WEBHOOK_URL, and FEISHU_WEBHOOK_SECRET.
  • If credentials are unavailable, produce setup instructions or a local stub instead of pretending the integration is live.

Common Use Cases

  • Bot webhook messages
  • App access token and tenant access token flows
  • Docs, Sheets, Wiki, and Bitable reads/writes
  • Approval or workflow status updates
  • Feishu/Lark MCP server configuration

Workflow

  1. Clarify whether the target is Feishu or Lark.
  2. Identify the credential type: webhook, internal app, marketplace app, or OAuth user token.
  3. Prefer official OpenAPI endpoints and signed webhooks when secrets are configured.
  4. For MCP, build or configure a server that exposes narrow tools such as send_message, read_doc, append_sheet_row, or query_bitable.
  5. Register the MCP server with deepseek mcp add, then run deepseek mcp validate and deepseek mcp tools.
  6. Verify with a dry run, sandbox document, or read-back call before sending externally visible messages.

Ask for confirmation before sending messages, writing production documents, or changing approval/workflow state.