lark-openapi-explorer

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 body. First mine the official docs at open.feishu.cn/llms.txt to confirm the exact path, parameters, and required permission scopes.

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 the individual API page. Never guess paths or parameters; always confirm them from the documentation.

Yes, lark-cli api supports GET, POST, PUT, PATCH, and DELETE with --params for query strings and --data for request bodies. Write and delete operations require explicit user confirmation before execution, and sensitive actions should explain their impact scope.

Feishu uses open.feishu.cn/llms.txt while Lark uses open.larksuite.com/llms.txt; both follow the same layered markdown structure. If the user's brand is unknown, default to the Feishu entry point.

Skip exploration when an existing lark-* skill or a registered lark-cli command already covers the need; check with lark-cli <service> --help first. Raw API calls are the fallback for uncovered functionality, not the default path.