CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lark-openapi-explorer

飞书/Lark 原生 OpenAPI 探索:从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口。当用户的需求无法被现有 lark-* skill 或 lark-cli 已注册命令满足,需要查找并调用原生飞书 OpenAPI 时使用。

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

A well-constructed skill body: executable WebFetch and CLI commands, a disciplined five-step discovery workflow with safety confirmation for write/delete operations, and clean delegation of shared concerns to lark-shared. The weaknesses are minor — a duplicated translation note, a hedged dry-run suggestion, and no explicit error-handling feedback loop.

DimensionReasoningScore

Conciseness

The body is lean — a doc-library tree diagram, a compact entry-URL table, five terse steps, and two worked examples — with no padding explaining concepts Claude already knows. Minor trimmable redundancy keeps it off the 5 anchor: the English-translation instruction appears twice ('如果用户使用英文交流,需将文档内容翻译为英文后输出' and again '如果用户使用英文交流,将以上所有内容翻译为英文'), and the brand URL rules are stated twice (table + Step 2 bullets).

4 / 5

Actionability

Fully executable throughout: each WebFetch step includes a concrete extraction question, the `lark-cli api` section gives copy-paste syntax for GET/POST/PUT/DELETE, and the two scenarios are complete end-to-end command sequences ('lark-cli api POST /open-apis/im/v1/chats/oc_xxx/members --data … --params …'). This matches the 5 anchor — copy-paste-ready commands with specific examples covering the common cases.

5 / 5

Workflow Clarity

Five strictly sequenced steps with an explicit anti-skip directive ('严格按以下步骤逐层检索,不要跳步或猜测 API'), a capability checkpoint at Step 1, and destructive-op confirmation in the safety rules ('写入/删除类 API 调用前必须确认用户意图') — so the destructive-operation cap at 3 does not apply since validation is present. It falls short of the 5 anchor because the dry-run safety valve is hedged ('如支持') and there is no error-recovery loop (nothing on handling error codes or failed calls), matching 'clear sequence with most checkpoints; minor validation gaps'.

4 / 5

Progressive Disclosure

Well-organized sections with clearly signaled one-level-deep cross-skill references — auth and safety detail delegated to [lark-shared](../lark-shared/SKILL.md) rather than duplicated, and a 参考 section listing both links with purpose. No bundle files exist to split content into; the inline material (tree diagram, two scenarios) is appropriately sized for SKILL.md. The 5 anchor is not fully met only because the cross-skill paths sit outside this bundle and cannot be verified, and the scenario examples could arguably live in a reference file — minor organization gaps per the 4 anchor.

4 / 5

Total

17

/

20

Passed

Description

87%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 strong description: concrete actions, an explicit and well-scoped use-when trigger, and clear differentiation from the related lark-* skills and CLI commands. The only gaps are minor keyword variations and slightly less-than-comprehensive action coverage.

DimensionReasoningScore

Specificity

Concrete actions are named — '从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口' and '需要查找并调用原生飞书 OpenAPI' — but coverage stops short of comprehensive (no hint of the doc-layering/search process or output form). It sits at 'several specific actions; minor gaps', above the 3 anchor (only 1-2 actions) but below the 5 anchor's full coverage.

4 / 5

Completeness

It clearly answers both parts: what ('从官方文档库中挖掘…原生 OpenAPI 接口') and an explicit use-when clause ('当用户的需求无法被现有 lark-* skill 或 lark-cli 已注册命令满足…时使用') with concrete trigger phrasing. This mirrors the 5 anchor's structure exactly; the 4 anchor requires a weaker or less explicit 'when', which is not the case here.

5 / 5

Trigger Term Quality

Good natural keyword coverage — '飞书/Lark', 'OpenAPI', 'lark-* skill', 'lark-cli', '原生' — terms a user of this skill family would naturally say. A few natural variations (e.g. '接口', 'API 调用', '未封装') are absent, so it matches 'good coverage; a few natural terms missing' rather than the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche and explicitly delimits it against siblings ('无法被现有 lark-* skill 或 lark-cli 已注册命令满足'), so it triggers only when those fail. Minimal conflict risk, matching the 5 anchor; the 4 anchor's 'minor overlap risk with closely related skills' is already ruled out by the explicit exclusion.

5 / 5

Total

18

/

20

Passed

Validation

75%

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

Validation — 12 / 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

relative_links

Relative link issues: 3 suspicious

Warning

Total

12

/

16

Passed

Repository

larksuite/cli

Path

skills/lark-openapi-explorer/SKILL.md

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.