lark-openapi-explorer

Discovers native Feishu/Lark OpenAPI endpoints from official documentation and invokes them via lark-cli.

Updated May 28, 2026
One-click install
npx skills add https://github.com/changfengpro/agent-skills --skill lark-openapi-explorer-changfengpro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-openapi-explorer
Source: https://github.com/changfengpro/agent-skills/tree/main/skills/lark-openapi-explorer
Command: npx skills add https://github.com/changfengpro/agent-skills --skill lark-openapi-explorer-changfengpro

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 request, this Skill locates the raw Feishu/Lark OpenAPI endpoint from the official markdown documentation library 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 docs step by step to find exact API 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 & Safety: Presents API name, method, path, parameters, required permission scopes, and call examples, with mandatory confirmation before write or delete operations. - Use Case: A user needs to add members to a group chat, but lark-cli im has no such 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 since no existing 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 lark-cli does not support?

Use this Skill to mine the official documentation at open.feishu.cn/llms.txt layer by layer until you find the exact API spec, then invoke it with lark-cli api using the appropriate HTTP method, path, and JSON payload.

How to find the right Lark API for a specific task?

Start from the top-level llms.txt index to locate the relevant module document, then fetch the module doc to find the specific API page, and finally retrieve the full spec including method, path, parameters, permissions, and error codes.

Does this work for both Feishu and Lark brands?

Yes. Feishu uses open.feishu.cn as the documentation entry while Lark uses open.larksuite.com. If the user's brand is unclear, the Skill defaults to the Feishu documentation site.

Is it safe to call write or delete APIs through lark-cli api?

The Skill requires explicit user confirmation before any POST, PUT, or DELETE call and explains the impact scope for sensitive operations like removing members. It never guesses API paths or parameters; everything is verified against official docs first.

When should I not use OpenAPI exploration?

Skip exploration whenever an existing lark-* skill or a registered lark-cli command already covers the need. Check with lark-cli <service> --help first, and only mine the documentation when no wrapped command exists.