CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lark-task

飞书任务:管理任务、清单和任务智能体。创建待办任务、查看和更新任务状态、拆分子任务、组织任务清单、分配协作成员、上传任务附件、注册或注销任务智能体、更新任务智能体的主页数据、写入智能体任务记录。当用户需要创建待办事项、查看任务列表、跟踪任务进度、管理项目清单或给他人分配任务、为任务上传附件文件、注册注销任务智能体、更新智能体主页数据、写入任务记录时使用。

Quality

81%

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

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

The body delivers a well-structured, schema-first CLI orchestration guide: a disciplined capability-discovery workflow with error-recovery loops, concrete commands, per-command reference files, and useful constraints (GUID vs display number, due/repeat_rule ordering). Its weaknesses are redundancy — the search-vs-list decision logic repeated three times and an inlined 40-line permission table — plus the absence of any caution/validation rule for destructive delete operations.

Suggestions

Merge the three near-duplicate search-decision blockquotes (任务搜索技巧 / 任务清单搜索技巧 / 意图区分补充) into a single decision rule stated once, noting it applies to both tasks and tasklists, to cut substantial repeated tokens.

Move the static permission table to a reference file (e.g., references/lark-task-permissions.md) and keep only the scope-lookup rule inline, since the body itself states that live CLI help/schema is authoritative and the table can drift.

Add a brief validation rule for destructive operations (tasks.delete, tasklists.delete), such as confirming the resolved task/list GUID with the user before executing the delete.

DimensionReasoningScore

Conciseness

The body is operational throughout with no explanations of concepts Claude already knows, but the search-vs-list decision logic is restated three times in near-verbatim blockquotes ("任务搜索技巧", "任务清单搜索技巧", "意图区分补充") and a ~40-line static permission table is inlined in the main file despite the body itself declaring live CLI help authoritative. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' better than the minor-trims anchor at 4.

3 / 5

Actionability

Concrete executable commands appear throughout ("lark-cli schema task.<resource>.<method>", "lark-cli task tasklists tasks --params '{\"tasklist_guid\":\"<tasklist_guid>\"}' --as user") alongside a discovery procedure tied to real CLI output. It falls short of the fully copy-paste-ready anchor at 5 because the most common cases (create, complete, assign) have no inline example and delegate entirely to reference files.

4 / 5

Workflow Clarity

The command-discovery flow is a numbered sequence with an explicit error-recovery loop ("遇到 unknown_subcommand 时必须停止猜测或尝试变体,回到第 2 步重新发现能力") and pre-execution validation ("调用 API 前必须先查看参数结构"), and the locate-and-modify path adds post-execution verification via returned server fields. It is not 5 because destructive operations (tasks.delete, tasklists.delete, comments.delete) are listed with no confirmation or validation guidance.

4 / 5

Progressive Disclosure

The body is a clear overview whose shortcut table maps each of 18 commands to its own dedicated reference file; all referenced files exist and link only back to SKILL.md and the shared skill (verified one level deep, no nested references). This matches the top anchor of a clear overview with well-signaled one-level-deep references and easy navigation.

5 / 5

Total

16

/

20

Passed

Description

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

The description is strong: it enumerates nine concrete, specific actions across tasks, tasklists, and task agents, and pairs them with an explicit, concrete 'use when' trigger clause in third-person voice. Its only weaknesses are a handful of missing natural trigger terms (search, complete, comment, delete, reminders) and slight overlap risk with the sibling meeting-minutes todo feature.

DimensionReasoningScore

Specificity

The description lists nine concrete actions ("创建待办任务、查看和更新任务状态、拆分子任务、组织任务清单、分配协作成员、上传任务附件、注册或注销任务智能体、更新任务智能体的主页数据、写入智能体任务记录") covering tasks, tasklists, and agents comprehensively. It matches the anchor for multiple specific concrete actions with comprehensive coverage; score 4 would require minor gaps, and none are evident within its stated scope.

5 / 5

Completeness

Both questions are explicitly answered: the 'what' is the concrete capability list, and the 'when' is the explicit trigger clause "当用户需要创建待办事项、查看任务列表、跟踪任务进度、管理项目清单或给他人分配任务…写入任务记录时使用" with concrete trigger phrases. This matches the top anchor; score 4 would require the 'when' to be less explicit or specific, which it is not.

5 / 5

Trigger Term Quality

Natural user phrases are present ("创建待办事项", "查看任务列表", "跟踪任务进度", "给他人分配任务") with synonyms like 待办/任务 and 任务列表/清单, but natural trigger terms for several supported capabilities are missing: 搜索 (search), 完成任务 (complete), 评论 (comment), 删除 (delete), and 提醒 (reminders). This fits the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive-synonyms anchor at 5.

4 / 5

Distinctiveness Conflict Risk

The niche is clearly named ("飞书任务:管理任务、清单和任务智能体") giving distinct domain triggers, but generic phrases like "创建待办事项" overlap with the closely related lark-meeting minutes-todo capability — the skill body itself needs a disambiguation section for it. This is 'mostly distinct; minor overlap risk with closely related skills' rather than the minimal-conflict anchor at 5.

4 / 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: 2 suspicious

Warning

Total

12

/

16

Passed

Repository

larksuite/cli

Path

skills/lark-task/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.