lark-openapi-explorer

Discover Feishu/Lark OpenAPI endpoints from official markdown documentation.

Updated Aug 17, 2024
One-click install
npx skills add https://github.com/LinoWhy/.dotfiles --skill lark-openapi-explorer-linowhy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-openapi-explorer
Source: https://github.com/LinoWhy/.dotfiles/tree/main/agents/.agents/skills/lark-openapi-explorer
Command: npx skills add https://github.com/LinoWhy/.dotfiles --skill lark-openapi-explorer-linowhy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When user needs to discover native Feishu/Lark OpenAPI endpoints that are not yet covered by existing skills or CLI commands, this skill guides the search from the official docs and prepares exact API call instructions.

Core Features & Use Cases

  • Layered OpenAPI discovery from the top-level index to module docs and individual API pages.
  • Provides complete call specifications: HTTP method, path, parameters, required scopes, and ready-to-run lark-cli api invocations.
  • Useful for validating uncovered APIs and expanding tool coverage when user requests go beyond registered commands.

Quick Start

Identify an unwrapped Feishu/Lark OpenAPI in the official docs and prepare a ready-to-run lark-cli api invocation.

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 Feishu or Lark OpenAPI endpoints not covered by existing CLI commands?

To discover unwrapped Feishu or Lark OpenAPI endpoints, search the official markdown documentation using a layered approach: navigating from the top-level index to module docs and individual API pages to extract exact call specifications.

What information is included in a Feishu OpenAPI discovery result?

A Feishu OpenAPI discovery result provides the exact HTTP method, API path, parameters, required permission scopes, and a ready-to-run lark-cli api invocation example for reliable endpoint execution.

How do I get a ready-to-run lark-cli command for a specific Lark API?

You can get a ready-to-run lark-cli command by identifying the target API in the official Lark docs; the extraction process maps the endpoint's HTTP method, path, and parameters directly into a CLI invocation.

Can I use this approach to validate OpenAPI coverage for automation workflows?

Yes, you can validate OpenAPI coverage for automation workflows by checking official Feishu markdown documentation to identify native endpoints when existing skills or CLI commands do not cover your requested automation actions.

When should I search official docs instead of using existing Feishu CLI commands?

You should search official docs when user requests go beyond registered commands, requiring you to discover native Feishu or Lark OpenAPI endpoints that are not yet covered by existing skills or CLI commands.