Documents & Data · IN-DEPTH PROFILE

lark-openapi-explorer

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-08-20

Pinned revision · 755daa4d

Open pinned commit ↗
SkillSignal profileSource-grounded

Updated 2026-08-20

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

30-SECOND BRIEF

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.

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 scope.claude/skills/lark-openapi-explorer/
Personal scope~/.claude/skills/lark-openapi-explorer/

Use project scope for team sharing and personal scope across repositories. The installer defaults to project scope; add -g for personal scope.

Install command (project scope)

This source cannot produce a reliable command. Open the listed source and copy the complete Skill folder manually.

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 Claude Code + Codex

grill-with-docs

Grill With Docs combines deep design questioning with domain-model documentation.
Tradeoff to check
It assumes the repository has, or is willing to adopt, domain glossaries and decision records.
First risk
Documentation churn · Medium
Source state
Pinned · 885e2ca4
Open profile ↗
02

Same job family · native to Claude Code + Codex

lark-approval

Lark Approval routes approval instances and approval inbox work through lark-cli.
Tradeoff to check
Available actions depend on the approval definition, current state, identity, and tenant permissions.
First risk
Consequential approval action · High
Source state
Pinned · 755daa4d
Open profile ↗
03

Same job family · native to Claude Code + Codex

lark-attendance

Lark Attendance is a narrow, read-only lark-cli Skill for querying the current user's Feishu attendance check-in records.
Tradeoff to check
The Skill only documents the user's own check-in query; it is not a general attendance administration tool.
First risk
Employment data exposure · High
Source state
Pinned · 755daa4d
Open 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.

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.