Agent Skills › XiaomingX/mimofan › feishu

feishu

GitHub

飞书/Lark集成技能，指导安全处理凭证、调用OpenAPI及配置MCP服务器。涵盖机器人消息、文档操作、审批流等场景，强调使用环境变量及沙箱验证，避免硬编码密钥。

crates/tui/assets/skills/feishu/SKILL.md XiaomingX/mimofan

Trigger Scenarios

用户请求飞书或Lark相关功能需要集成飞书API或配置MCP服务

Install

npx skills add XiaomingX/mimofan --skill feishu -g -y

More Options

Non-standard path

npx skills add https://github.com/XiaomingX/mimofan/tree/main/crates/tui/assets/skills/feishu -g -y

Use without installing

npx skills use XiaomingX/mimofan@feishu

指定 Agent (Claude Code)

npx skills add XiaomingX/mimofan --skill feishu -a claude-code -g -y

安装 repo 全部 skill

npx skills add XiaomingX/mimofan --all -g -y

预览 repo 内 skill

npx skills add XiaomingX/mimofan --list

SKILL.md

Frontmatter

{
    "name": "feishu",
    "description": "Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI\/MCP setup without hardcoding credentials."
}

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

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