CtrlK
BlogDocsLog inGet started
Tessl Logo

lark-base

飞书多维表格(Base)操作:建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、workflow、角色权限;遇到 Base/多维表格/bitable 或 /base/ 链接时使用。文件导入转 lark-drive,认证/授权转 lark-shared。

78

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is a lean, actionable routing overview with concrete commands, explicit validation/confirmation checkpoints for risky operations, and a clean one-level-deep reference structure. It earns top scores across conciseness, actionability, workflow clarity, and progressive disclosure.

DimensionReasoningScore

Conciseness

The body is dense and action-oriented — routing tables, ID/token prerequisites, error-recovery tables — with no explanation of concepts Claude already knows; every line earns its place and assumes Claude's competence, matching the lean level-3 anchor.

3 / 3

Actionability

It gives concrete, copy-paste-ready commands with exact flags (e.g. "lark-cli base +url-resolve --url ... --as user", "+base-create --table-name ... --fields ...", `--yes` gates) and specific error-code recovery actions, beyond the incomplete/pseudocode level-2 anchor.

3 / 3

Workflow Clarity

Multi-step processes are explicitly sequenced with validation checkpoints: token+ID acquisition first, read-modify-write before updates, confirmation gates for destructive ops, batch limits and `1254291` retry handling, plus a recovery table — meeting the clear-sequence-with-validation level-3 anchor rather than the checkpoint-missing level-2.

3 / 3

Progressive Disclosure

The SKILL.md body is an overview routing to well-signaled one-level-deep references, all of which resolve to real files in ./references/, with a dedicated "保留 Reference" index — matching the clear-overview level-3 anchor and avoiding nested-reference or monolithic patterns.

3 / 3

Total

12

/

12

Passed

Description

100%

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

The description is specific, trigger-rich, and complete with explicit when-guidance plus routing to avoid sibling-skill conflicts. It scores top across all four dimensions with no padding or vague language.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、workflow、角色权限" — matching the level-3 anchor of several specific concrete actions, and is not the level-2 single-domain partial list.

3 / 3

Completeness

Explicitly answers both what (the enumerated Base operations) and when ("遇到 Base/多维表格/bitable 或 /base/ 链接时使用"), satisfying the level-3 anchor and avoiding the missing-trigger cap.

3 / 3

Trigger Term Quality

Covers natural user terms users would actually say — "Base/多维表格/bitable 或 /base/ 链接" — giving good coverage of common variations, not the sparse level-2 "Works with PDF files" style.

3 / 3

Distinctiveness Conflict Risk

Has a clear niche (Feishu Base/bitable) with explicit de-confliction routing — "文件导入转 lark-drive,认证/授权转 lark-shared" — making it unlikely to trigger the wrong skill, which is beyond the still-overlapping level-2 anchor.

3 / 3

Total

12

/

12

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.