Documents & Data · IN-DEPTH PROFILE

lark-base

Lark Base covers structured operations on Feishu Base (Bitable), including tables, fields, records, views, and related data workflows after a Base exists.

Best for

Operations teams using Feishu Base

What you get

Inspect schema + Manage records

Main limitation

Field types, permissions, and automation behavior vary between Bases and must be inspected first.

First risk

Bulk data changes. Record and field operations can affect shared business data. Use filters, small batches, and a reversible test first.

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 Base covers structured operations on Feishu Base (Bitable), including tables, fields, records, views, and related data workflows after a Base exists. It should be paired with the shared authentication rules, while file-to-Base imports are routed through Lark Drive before table-level work begins.

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

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

Inspect schema

Read tables, fields, views, and record shapes before acting.

02

Manage records

Query, create, update, or organize structured Base data.

03

Coordinate imports

Hand file conversion to Drive, then continue with table-level operations.

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. Field types, permissions, and automation behavior vary between Bases and must be inspected first.
  2. Large batch operations need explicit pagination and error handling.

BEST FIT

Who it is for

Operations teams using Feishu Base

Agents maintaining structured business data

BEFORE YOU USE IT

Risks to review before use

High

Bulk data changes

Record and field operations can affect shared business data. Use filters, small batches, and a reversible test first.

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

feishubitablerecords

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.