lark-openapi-explorer

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

2|Updated Aug 9, 2026
One-click install
npx skills add https://github.com/DeepJH/doubao-skill-and-info --skill lark-openapi-explorer-deepjh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-openapi-explorer
Source: https://github.com/DeepJH/doubao-skill-and-info/tree/main/skills/lark-openapi-explorer
Command: npx skills add https://github.com/DeepJH/doubao-skill-and-info --skill lark-openapi-explorer-deepjh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires lark-cli.

What problem does it solve? When existing lark-* skills or lark-cli registered commands cannot fulfill a Feishu/Lark automation need, this Skill locates the underlying native OpenAPI endpoint in the official documentation and calls it directly, so you are never blocked by missing CLI wrappers. ## Core Features & Use Cases - Layered Documentation Mining: Traverses the official llms.txt index, module documents, and individual API markdown pages to find exact API specifications without guessing. - Raw API Invocation: Executes discovered endpoints via lark-cli api with GET, POST, PUT, PATCH, and DELETE methods, including path parameters, query strings, and request bodies. - Structured Output: Reports API name, HTTP method and path, required parameters, permission scopes, call examples, and rate-limit notes, translated to English when needed. - Use Case: A user wants to add members to a Feishu group chat, but lark-cli has no chat_members create command. The Skill mines the docs to find POST /open-apis/im/v1/chats/:chat_id/members and invokes it with the correct id_list payload. ## Quick Start Find the native Feishu OpenAPI for setting a group chat announcement and call it for chat oc_xxx.

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 not covered by lark-cli?

Use lark-cli api with the HTTP method and path, for example lark-cli api POST /open-apis/im/v1/chats/:chat_id/members with a --data JSON payload. First mine the official docs at open.feishu.cn/llms.txt to confirm the exact path, parameters, and required scopes.

How to find the right Feishu API in the official documentation?

Fetch https://open.feishu.cn/llms.txt to list module documents, then fetch the relevant llms-<module>.txt file to locate the specific API page. Each API markdown page contains the method, path, parameters, response fields, permissions, and error codes.

Does this work for both Feishu and Lark brands?

Yes. Feishu documentation is served from open.feishu.cn and Lark documentation from open.larksuite.com, both following the same llms.txt structure. If the brand is unknown, the workflow defaults to Feishu.

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

Only when lark-cli --help shows no registered command or shortcut for your task. Existing wrapped commands are preferred; raw api calls are the fallback for uncovered endpoints like chat announcements or member management.

Is it safe to run write or delete OpenAPI calls on Feishu?

Write and delete calls (POST, PUT, DELETE) require explicit user confirmation before execution, and sensitive operations like removing members should include an explanation of impact. Never guess API paths or parameters; always confirm them from the official documentation first.