lark-openapi-explorer

Discover Lark/Feishu OpenAPI endpoints from official Markdown documentation and execute via lark-cli api.

Updated Sep 4, 2025
One-click install
npx skills add https://github.com/ykai55/dotfiles --skill lark-openapi-explorer-ykai55
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-openapi-explorer
Source: https://github.com/ykai55/dotfiles/tree/main/opencode/skills/lark-openapi-explorer
Command: npx skills add https://github.com/ykai55/dotfiles --skill lark-openapi-explorer-ykai55

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

When your need isn’t covered by existing lark-* skills or by lark-cli’s registered commands, this Skill helps you find the correct native OpenAPI endpoint from Feishu/Lark’s official Markdown document library instead of guessing.

Core Features & Use Cases

  • Step-by-step API discovery: Locates the right module from the top index, then drills down to the specific API Markdown, and finally extracts the complete HTTP method, path, parameters, request/response fields, scopes, and error codes.
  • Direct execution via CLI: Uses lark-cli api to call the discovered OpenAPI endpoint with the exact data structure from the documentation.
  • Safety-first output: Presents method/path, required parameters, permissions, example command, and safety notes, and adds guardrails for write/delete operations.

Quick Start

Ask the AI to “find the native Feishu/Lark OpenAPI for <your feature> that isn’t supported by lark-cli <service> and return the exact lark-cli api command with required parameters and permissions.”

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 Lark OpenAPI that isn't covered by existing lark-cli commands?

Discover native Lark OpenAPI endpoints by traversing the official Markdown document library to extract HTTP methods, paths, and parameters, then execute calls safely via lark-cli instead of guessing endpoints.

What is the safest way to discover and execute Lark OpenAPI write or delete operations?

The safest way to execute Lark OpenAPI write or delete operations is by extracting the exact invocation specification from official Markdown docs and using a safety-first approach that applies guardrails to the lark-cli api command for destructive requests.

How do I find the correct HTTP method and path for a specific Feishu API from documentation?

Find the correct Feishu API HTTP method and path by traversing the official Markdown API library index to the module documentation, extracting the complete invocation specification including parameters and scopes.

Do I need lark-cli installed to discover and call native Lark APIs?

Yes, lark-cli is required to execute discovered native Lark OpenAPI endpoints, serving as the runtime environment to invoke HTTP calls with exact data structures extracted from official Markdown documentation.

Can I use this approach to automate Lark API calls without guessing endpoints?

Yes, you can automate Lark API calls without guessing by applying a strict, non-guessing traversal of the official Markdown API library to extract the full invocation specification and executing the request via lark-cli.

What limitations exist when discovering Feishu APIs through the Markdown document library?

The limitation is that discovering Feishu APIs through the Markdown document library is strictly for operations not covered by existing lark skills or lark-cli commands, requiring manual extraction of parameters, scopes, and error codes before execution.