lark-openapi-explorer

Discover Feishu/Lark OpenAPI endpoints from official markdown docs and generate lark-cli api calls.

1|Updated May 17, 2026

Search Tags:#automation #openapi #lark #web fetch #lark-cli #safety guardrails #api discovery

Ready to run

npx skills add https://github.com/mykcs/myk-skills --skill lark-openapi-explorer-mykcs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lark-openapi-explorer
Source: https://github.com/mykcs/myk-skills/tree/main/lark-openapi-explorer
Command: npx skills add https://github.com/mykcs/myk-skills --skill lark-openapi-explorer-mykcs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires lark-cli, and includes references (resource) components.

What problem does it solve?

When Lark/Lark CLI doesn’t provide a built-in command for a needed operation, this Skill helps you find the correct native OpenAPI endpoint and call it directly.

Core Features & Use Cases

Document-driven API discovery: Walks the official markdown doc index layer-by-layer (modules → specific API docs) instead of guessing paths or parameters.
Native request execution via lark-cli: Calls the discovered endpoint using lark-cli api with the right HTTP method, path parameters, query params, and body fields.
Safety-first operation guidance: Enforces confirmation and guardrails for write/delete operations and requires document-sourced specifications.

Quick Start

Ask the Skill to locate the correct native OpenAPI endpoint for your Lark task and then generate the exact lark-cli api command to run it, based strictly on the official markdown docs for your chosen brand (Feishu/Lark).

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 Lark OpenAPI endpoint when there is no built-in command?▼

You can call a Lark OpenAPI endpoint by discovering the correct native API specification through official markdown docs and executing it directly via the lark-cli api command. This ensures precise GET, POST, PUT, or DELETE operations without guessing paths or parameters.

How do I find the correct path and parameters for a Feishu OpenAPI request?▼

To find the correct Feishu OpenAPI request details, retrieve the official module index and walk through specific API markdown documentation layer-by-layer. This document-driven discovery process ensures you source the exact method, path, required parameters, and permissions accurately.

Does lark-cli support executing native OpenAPI operations safely?▼

Yes, lark-cli supports executing native OpenAPI operations safely by enforcing confirmation guardrails for write and delete operations. It requires document-sourced specifications to generate the exact API call, preventing unauthorized or incorrect modifications to your Lark environment.

What is the best way to automate Lark tasks not covered by existing skills?▼

The best way to automate uncovered Lark tasks is to use document-driven API discovery to locate the required native OpenAPI endpoint. Then, generate a complete lark-cli api command based strictly on the official markdown specification to execute the automation safely.

When should I not use direct OpenAPI calls for Lark automation?▼

You should not use direct OpenAPI calls if an existing Lark skill or lark-cli command already covers your requirement. Direct API execution should be reserved for specific scenarios where built-in commands lack the functionality needed for your precise automation task.

Can I use lark-cli to perform GET and POST requests on Lark APIs?▼

Yes, you can use lark-cli to perform GET, POST, PUT, and DELETE requests on Lark APIs. It constructs the native request execution using the discovered HTTP method, path parameters, query parameters, and body fields extracted directly from official API documentation.