lark-openapi-explorer

Discovers and invokes native Feishu/Lark OpenAPI endpoints from official documentation.

8|2|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/luojiaaoo/xpeech --skill lark-openapi-explorer-luojiaaoo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lark-openapi-explorer
Source: https://github.com/luojiaaoo/xpeech/tree/main/xpeech/agent/skills/buildin/lark-skills/lark-openapi-explorer
Command: npx skills add https://github.com/luojiaaoo/xpeech --skill lark-openapi-explorer-luojiaaoo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When existing lark-* skills or lark-cli registered commands cannot fulfill a Feishu/Lark automation request, this Skill locates the underlying native OpenAPI endpoint in the official documentation and calls it directly, eliminating the need to manually search API docs. ## Core Features & Use Cases - Layered Documentation Mining: Traverses the official llms.txt index, module documents, and individual API pages to find exact endpoint specifications without guessing. - Raw API Invocation: Executes discovered endpoints through lark-cli api with GET, POST, PUT, PATCH, and DELETE methods, including path parameters, query strings, and request bodies. - Structured Output: Presents each discovered API with its method, path, required parameters, permission scopes, a ready-to-run command example, and rate-limit notes. - Use Case: A user asks to add members to a Feishu group chat, but lark-cli has no registered command for it. The Skill mines the docs, finds POST /open-apis/im/v1/chats/:chat_id/members, and invokes it with the correct open_id list. ## Quick Start Ask the agent to find and call the native Feishu OpenAPI endpoint for a task that the existing lark-cli commands do not cover, such as setting a group chat announcement.

Frequently Asked Questions about lark-openapi-explorer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I call a Feishu OpenAPI endpoint that lark-cli does not support?▼

Use lark-cli api with the HTTP method and path, for example lark-cli api POST /open-apis/im/v1/chats/oc_xxx/members with a --data JSON body. First confirm via lark-cli <service> --help that no registered command already covers the task.

How to find the right Feishu OpenAPI endpoint in the official docs?▼

Start from the top-level index at https://open.feishu.cn/llms.txt, then fetch the relevant module document, and finally the individual API markdown page. Each layer narrows down to the exact method, path, parameters, and required permission scopes.

Does this work for Lark international accounts or only Feishu?▼

Both brands are supported. Feishu documentation is served from open.feishu.cn and Lark documentation from open.larksuite.com. If the user's brand is unknown, the workflow defaults to the Feishu documentation entry point.

What safety checks apply before calling write or delete Feishu APIs?▼

Write and delete operations (POST, PUT, DELETE) require explicit user confirmation before execution. Sensitive actions like removing group members should include an explanation of the impact scope, and API paths must come from documentation rather than guesses.

When should I use raw OpenAPI calls instead of existing lark-cli commands?▼

Only when lark-cli --help shows no registered command or shortcut for the task. Existing commands are preferred because they are already wrapped and validated; raw API mining is the fallback for uncovered functionality.