Documents & Data · IN-DEPTH PROFILE

Lark Openapi Explorer Skill

Lark OpenAPI Explorer is a fallback workflow for capabilities not covered by an existing lark-* Skill or registered CLI command.

View listed source ↗Installation guide ↓
Best for

Developers integrating less common Feishu APIs

What you get

Find an uncovered API + Extract a call contract

Main limitation

It should not replace a maintained domain Skill or CLI shortcut that already covers the operation.

First risk

Raw API side effects. A verified endpoint can still delete, publish, or change shared resources. Preview when possible and obtain explicit approval for POST, PUT, PATCH, or DELETE operations.

EVIDENCE FRESHNESS

Three checks, kept separate

A recent source check is not a runtime test or security audit.

Upstream sourceChecked 2026-09-23

Pinned revision · a079fd7a

Open pinned commit ↗
SkillSignal profileSource-grounded

Updated 2026-08-20

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

IN PLAIN ENGLISH

What it does—and when it fits

Lark OpenAPI Explorer is a fallback workflow for capabilities not covered by an existing lark-* Skill or registered CLI command. It walks Feishu's official llms.txt hierarchy from module index to an individual API specification, extracts method, path, parameters, scopes, responses, and errors, then makes a raw request through lark-cli api without guessing fields.

This is aimed at Developers integrating less common Feishu APIs. Compare the examples below with your task, then review the limitations, permissions, and risks before installing.

What you get
  • Find an uncovered APIConfirm the CLI gap, locate the relevant official module, and identify the exact endpoint.
  • Extract a call contractCapture required parameters, scopes, response fields, errors, and rate-limit notes from the API page.
  • Call through lark-cliIssue a raw authenticated request only after the official contract has been verified.
What makes it different
  • This profile is manually organized around the current upstream SKILL.md workflow.
  • The capability boundary remains explicitly tied to open.feishu.cn.
  • Core uses, limitations, and risks are separated for pre-install review.
Community signalskills.sh All-time: #31 · 727.8K installs

No verified review text is in the current dataset. Use the linked source for the latest discussion.

Read the source note ↗

INSTALL BY AGENT

Choose your Agent

Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.

Native

This Skill's current record explicitly names this Agent. Still inspect scripts, permissions, and external dependencies first.

Project install (recommended)
npx skills add larksuite/cli --skill lark-openapi-explorer --agent claude-code
Personal install
npx skills add larksuite/cli --skill lark-openapi-explorer --agent claude-code -g

Project install stays with this repository for team sharing. Personal install adds -g and works across repositories.

This command adds the Skill instructions only. Install lark-cli and sign in to Feishu separately before use. Official Lark CLI setup ↗

View install paths
Project path.claude/skills/lark-openapi-explorer/
Personal path~/.claude/skills/lark-openapi-explorer/
Official agent docs

Claude Code discovers custom Skill folders automatically at project or personal scope.

View path evidence ↗

TYPICAL WORKFLOW

A practical workflow

01

Find an uncovered API

Confirm the CLI gap, locate the relevant official module, and identify the exact endpoint.

02

Extract a call contract

Capture required parameters, scopes, response fields, errors, and rate-limit notes from the API page.

03

Call through lark-cli

Issue a raw authenticated request only after the official contract has been verified.

THE TRADEOFFS

Advantages and tradeoffs

Notable strengths

  1. This profile is manually organized around the current upstream SKILL.md workflow.
  2. The capability boundary remains explicitly tied to open.feishu.cn.
  3. Core uses, limitations, and risks are separated for pre-install review.

Limitations

  1. It should not replace a maintained domain Skill or CLI shortcut that already covers the operation.
  2. Official documentation can still omit tenant-specific policy and runtime behavior that must be tested safely.

COMPARE THE TRADEOFF

Consider these close alternatives

These are deterministic nearby candidates, not paid placements or a universal ranking. Open the full profile before choosing.

01

Same job family · native to Codex + Claude Code

create-llms

Create an llms.txt index from repository documentation.
Tradeoff to check
Detailed package files are not fully catalogued.
First risk
Review before install · Medium
Source state
Pinned · 1f564408
Open create-llms profile ↗
02

Same job family · native to Codex + Claude Code

csharp-docs

Write useful XML documentation for C# APIs.
Tradeoff to check
Detailed package files are not fully catalogued.
First risk
Review before install · Medium
Source state
Pinned · 1f564408
Open csharp-docs profile ↗
03

Same job family · native to Codex + Claude Code

java-docs

Write consistent Javadoc for Java types and APIs.
Tradeoff to check
Detailed package files are not fully catalogued.
First risk
Review before install · Medium
Source state
Pinned · 1f564408
Open java-docs profile ↗
Compare more in the directory →

BEST FIT

Who it is for

→

Developers integrating less common Feishu APIs

→

Agents extending a workflow beyond registered commands

BEFORE YOU USE IT

Risks to review before use

High

Raw API side effects

A verified endpoint can still delete, publish, or change shared resources. Preview when possible and obtain explicit approval for POST, PUT, PATCH, or DELETE operations.

High

External data and identity boundary

Requests access Feishu tenant resources. Use the correct identity, least-privilege scopes, and keep sensitive content out of logs.

SECURITY

What the permission profile means

  • Declared access remains governed by the current upstream SKILL.md and runtime requests.
  • Treat Feishu documents, messages, people, and business records as permission-controlled data.
  • SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.

Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.

COMMON QUESTIONS

Lark Openapi Explorer Skill FAQ

What is the Lark Openapi Explorer Skill?

Lark OpenAPI Explorer is a fallback workflow for capabilities not covered by an existing lark-* Skill or registered CLI command. It walks Feishu's official llms.txt hierarchy from module index to an individual API specification, extracts method, path, parameters, scopes, responses, and errors, then makes a raw request through lark-cli api without guessing fields.

How do I install the Lark Openapi Explorer Skill?

Open and review the listed source, choose the project or personal path for your Agent, then verify the first run in a controlled project. Open the listed source and read the current SKILL.md plus only the references required for this task.

Is the Lark Openapi Explorer Skill safe to use?

SkillSignal checked the source on 2026-09-23, but that is not a runtime test or security certification. Review the “Raw API side effects” risk first and begin with the least access required.

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream Skill instructionsSource-linked

TAGS

feishuopenapiapi-discovery

Manually expanded from the current upstream SKILL.md and linked source at open.feishu.cn, checked 2026-08-19. This is an original summary, not an execution result or security certification.