lark-mail

飞书邮箱：Use when user mentions 起草邮件、写邮件、草稿、发送/回复/转发邮件、查阅邮件、看邮件、搜索邮件、邮件文件夹、邮件标签、邮件联系人、监听新邮件、邮件收信规则等；use for mail/email intent only. Do not use for docs/sheets/calendar/auth setup/pure contact lookup/IM chat tasks.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%

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

A highly actionable, well-structured skill body with clear workflows, validation checkpoints, and proper progressive disclosure to real bundle files. The main weakness is redundancy: the send-confirmation guidance is repeated across several sections and could be consolidated.

Suggestions

Consolidate the repeated send-confirmation rule into one canonical statement in '安全规则' and reference it from '数据真实性', '典型工作流', and '命令选择' instead of restating it each time.

Consider moving the detailed '原生 API 调用规则' (Step 1–3 + examples) into a dedicated reference file, keeping only the discovery workflow and the params/data mapping in SKILL.md.

Tighten the security section by merging overlapping items (e.g. #5 send-confirmation and #6 draft-vs-sent) to reduce token cost while preserving the rules.

Dimension	Reasoning	Score
Conciseness	The body is dense and free of concepts Claude already knows, but the send-confirmation rule is restated across '安全规则' #5/#6, '数据真实性' §2, '典型工作流', and '命令选择', and the confirmation messaging could be tightened into one canonical statement; not every token earns its place.	2 / 3
Actionability	Provides fully executable CLI commands with exact flags (e.g. 'lark-cli mail +send --to … --subject … --body …'), a concrete schema-lookup workflow, and copy-paste-ready bash blocks, matching the anchor for fully executable guidance.	3 / 3
Workflow Clarity	The 11-step '典型工作流' is clearly sequenced with explicit validation checkpoints (send_status confirmation, draft-before-send, '找不到就报未找到', batch-preview counts), satisfying the anchor for clear sequence with validation and feedback loops.	3 / 3
Progressive Disclosure	Body acts as an overview with well-signaled, one-level-deep references to real files in references/*.md (all present) and assets/templates/ (5 real HTML templates), with clear 'ref:' navigation; no deeply nested reference chains.	3 / 3
	Total	11 / 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.

A strong, specific description with explicit trigger terms, a clear 'Use when' clause, and explicit negative scope that minimizes conflict with adjacent skills. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists many concrete mail actions — '起草邮件、写邮件、草稿、发送/回复/转发邮件、查阅邮件、看邮件、搜索邮件、邮件文件夹、邮件标签、邮件联系人、监听新邮件、邮件收信规则' — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly states both what ('飞书邮箱' plus the action list) and when ('Use when user mentions …'), and the required 'Use when' clause is present so completeness is not capped at 2.	3 / 3
Trigger Term Quality	Uses natural phrasings a user would actually say (写邮件、发送/回复/转发邮件、看邮件、搜索邮件) with good coverage of common variations, matching the high-coverage anchor.	3 / 3
Distinctiveness Conflict Risk	Scoped to 'mail/email intent only' with an explicit exclusion list ('Do not use for docs/sheets/calendar/auth setup/pure contact lookup/IM chat tasks'), giving a clear niche unlikely to conflict with sibling skills.	3 / 3
	Total	12 / 12 Passed

Validation

75%

Warnings & errors only

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

Criteria	Description	Result
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: 1 suspicious	Warning

	Total	12 / 16 Passed

Repository: larksuite/cli
Path: skills/lark-mail/SKILL.md
Commit: a7865cd

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.