lark-openapi-explorer

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

1.3k|142|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/MiniMax-AI/minimax-code --skill lark-openapi-explorer-minimax-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lark-openapi-explorer
Source: https://github.com/MiniMax-AI/minimax-code/tree/main/packages/local-runtime/assets/skills/lark-tools/cli-skills/lark-openapi-explorer
Command: npx skills add https://github.com/MiniMax-AI/minimax-code --skill lark-openapi-explorer-minimax-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When existing lark-* skills or registered lark-cli commands cannot fulfill a request, this Skill locates the underlying native Feishu/Lark OpenAPI endpoint in the official documentation and calls it directly, so no platform capability is out of reach. ## 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 via lark-cli api with GET, POST, PUT, PATCH, and DELETE methods, including path parameters, query strings, and request bodies. - Structured Output: Reports each API's method, path, required parameters, permission scopes, and a ready-to-run command example. - Use Case: A user asks to add members to a Lark group chat, but no CLI command exists. The Skill mines the docs, finds POST /open-apis/im/v1/chats/:chat_id/members, and invokes it with the correct id_list payload. ## Quick Start Ask the assistant to find and call the native Feishu OpenAPI for adding members to a group chat since no existing lark-cli command covers it.

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 has no CLI command?▼

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 Lark OpenAPI endpoint for a task?▼

Start from the top-level index at open.feishu.cn/llms.txt (or open.larksuite.com/llms.txt for Lark), fetch the relevant module document, then open the specific API markdown page. Never guess paths or parameters; always confirm them from the documentation.

Does lark-cli support both Feishu and Lark brands?▼

Yes, the same lark-cli api command works for both, but the documentation entry point differs: open.feishu.cn for Feishu and open.larksuite.com for Lark. Default to Feishu if the user's brand is unknown.

When should I use raw API calls instead of existing lark skills?▼

Only when existing lark-* skills or registered lark-cli commands cannot satisfy the request. Always check lark-cli <service> --help first; if a command or shortcut already exists, use it directly instead of mining documentation.

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

Confirm user intent before any POST, PUT, or DELETE call, and explain the impact scope for sensitive operations like removing members or deleting groups. Use --dry-run to preview requests when supported.