lark-openapi-explorer

Locate native Feishu/Lark OpenAPI endpoints from official documentation.

3|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/agent-pilot/agent-pilot-be --skill lark-openapi-explorer-agent-pilot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-openapi-explorer
Source: https://github.com/agent-pilot/agent-pilot-be/tree/main/backend/skills/lark-openapi-explorer
Command: npx skills add https://github.com/agent-pilot/agent-pilot-be --skill lark-openapi-explorer-agent-pilot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify native Feishu/Lark OpenAPI endpoints from official documentation when existing skills or CLI do not cover the user’s request. It searches and verifies endpoints before attempting a raw API call.

Core Features & Use Cases

  • Layered discovery: traverses the official Markdown doc library from the top-level index llms.txt to module docs and individual API docs to locate bona fide OpenAPI endpoints.
  • No guesswork: ensures accuracy by strictly following documented paths, parameters, and responses.
  • API-ready guidance: after discovery, prepares the exact lark-cli api invocation to call the endpoint directly.
  • Use case: when you need a native OpenAPI call not yet exposed by any lark-* skill or existing CLI command.

Quick Start

Describe your OpenAPI need and I will locate the native Feishu/Lark endpoints in the official docs and outline the bare API call plan with lark-cli api.

Frequently Asked Questions about lark-openapi-explorer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find native Feishu OpenAPI endpoints not covered by existing skills?

Find native Feishu OpenAPI endpoints by traversing the official documentation library from the top-level index down to individual API docs, ensuring accurate endpoint discovery without guesswork. It locates bona fide endpoints when existing skills fall short.

What is the best way to verify undocumented Lark API paths before making a call?

The best way to verify Lark API paths is a hierarchical search of the official Markdown doc library, checking the top-level index and module docs to ensure you strictly follow documented paths, parameters, and responses without guessing unsupported routes.

How do I prepare a lark-cli api invocation after locating an endpoint?

After locating the correct endpoint in the documentation, the system prepares the exact raw lark-cli api invocation directly, providing API-ready guidance for the specific endpoint without introducing unsupported paths or parameters.

Does this OpenAPI discovery method support guessing endpoints for missing features?

No, this OpenAPI discovery method strictly avoids guesswork by ensuring accuracy through documented paths and parameters. It searches and verifies endpoints in official documentation before attempting any raw API call.

When do I need to search the official Feishu documentation for OpenAPI endpoints?

You need to search the official Feishu documentation for OpenAPI endpoints when you require a native OpenAPI call that is not yet exposed by any existing lark-* skill or current CLI command.