CtrlK
BlogDocsLog inGet started
Tessl Logo

lark-base

飞书多维表格(Base)操作:建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式(BaseApp/AppMode 页面与组件)、Workspace 目录、workflow、角色权限、模板中心(多维表格模板分类/列表/搜索);遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps;文件导入/导出转 lark-drive,认证/授权转 lark-shared。

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An action-dense, well-sequenced skill body with executable commands and explicit validation for batch/destructive operations. The main gap is minor: several existing reference files are not linked from the overview, slightly weakening discoverability.

Suggestions

Link the nine orphan reference files (e.g. lark-base-dashboard-block-config.md, lark-base-field-formula.md, lark-base-field-lookup.md, lark-base-role-config.md, lark-base-workflow-schema.md, lark-base-view-set-filter.md, lark-base-data-query.md) from the relevant body sections so all bundle materials are discoverable from the overview.

De-duplicate the 'read current state, modify one field at a time, confirm with write response' contract — state it once in 通用执行契约 and reference it from the Dashboard/Form/AdvPerm sections instead of restating.

Consolidate or trim the repeated异步读取-vs-写入确认 guidance in the Table section into a single concise checkpoint.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence with no basic-concept padding, but the read-modify-write/confirm contract and 'read current state before each update' guidance recur across several sections and could be tightened.

4 / 5

Actionability

Copy-paste-ready lark-cli commands with concrete flags appear throughout, alongside real JSON filter and CellValue examples that cover common cases, matching the fully-executable top anchor.

5 / 5

Workflow Clarity

Entry-point resolution is sequenced (four numbered paths), and destructive/batch operations carry explicit validation checkpoints (单批最多 200 条分批, 异步状态轮询, has_more=false 完整性判断, --keep-field 防止误删底层 Field), meeting the feedback-loop bar.

5 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep markdown-link references, all 17 linked files verified present; however nine reference files exist in the bundle but are not surfaced from the body, a minor organization gap.

4 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A highly specific, third-person description that clearly states both capabilities and trigger conditions while proactively disambiguating from neighboring skills. Only slightly short of maximal trigger-term breadth due to a few missing synonyms.

DimensionReasoningScore

Specificity

The description enumerates many concrete capabilities (建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式、Workspace 目录、workflow、角色权限、模板中心), matching the 'multiple specific concrete actions; comprehensive coverage' anchor.

5 / 5

Completeness

It explicitly answers both 'what' (the enumerated operations) and 'when' (遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用) with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural trigger terms are present with synonyms (Base/多维表格/bitable) and link patterns (/base/、/app/), but a few natural English variations and file extensions are missing, falling just below the comprehensive-synonym anchor of 5.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche and adds explicit routing-out guidance (BaseApp 不走 lark-apps;文件导入/导出转 lark-drive,认证/授权转 lark-shared), minimizing conflict with adjacent skills.

5 / 5

Total

19

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
larksuite/cli
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.