CtrlK
BlogDocsLog inGet started
Tessl Logo

lark-okr

飞书 OKR:管理目标与关键结果。查看和编辑 OKR 周期、目标、关键结果、对齐关系、量化指标和进展记录。当用户需要查看或创建 OKR、管理目标和关键结果、查看对齐关系时使用。不负责:待办任务管理(lark-task)、日程/会议安排(lark-calendar)、绩效评估

68

Quality

84%

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

80%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-structured, actionable skill body with strong progressive disclosure and executable examples. The main gap is missing explicit validation/verification checkpoints for batch and destructive operations, which caps workflow clarity.

Suggestions

Add explicit validation/verification steps after batch-create and indicator-update (e.g. confirm the returned OKR IDs and re-fetch cycle-detail before declaring success) to establish a validate-then-proceed loop.

Collapse the overlap between the 快速决策 decision table and the Shortcuts table, or cross-reference one from the other, to reduce redundancy and tighten token use.

Make the multi-step 'view OKR' and 'write OKR' flows into numbered sequences with checkpoints rather than only implying them via the decision table.

DimensionReasoningScore

Conciseness

The body is mostly lean — a decision table, shortcut list, and executable command examples assume Claude's competence; minor repetition between the 快速决策 table and Shortcuts table could be trimmed.

4 / 5

Actionability

Copy-paste-ready lark-cli commands with concrete flags and JSON payloads (cycle-list, cycle-detail, batch-create, indicator-update, search-user) cover the common cases with executable specifics.

5 / 5

Workflow Clarity

The 快速决策 table gives decision paths but the multi-step OKR workflows (e.g. view→create→update) lack explicit validation checkpoints; for batch-create and indicator-update there is no validate/verify-then-proceed feedback loop, which caps the score at 3 per the destructive/batch guidance.

3 / 5

Progressive Disclosure

Clear overview SKILL.md with well-signaled one-level-deep references to real files in references/ (entities, contentblock, per-verb docs); navigation is easy and content is appropriately split across 25 reference files.

5 / 5

Total

17

/

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.

A strong, specific description that clearly states capabilities, trigger conditions, and out-of-scope areas. Trigger term coverage is the only minor weakness, leaning on a limited set of phrasings.

Suggestions

Add a couple more natural user phrasings or synonyms for OKR tasks (e.g. '设定目标', '更新进度', '对齐目标') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — '查看和编辑 OKR 周期、目标、关键结果、对齐关系、量化指标和进展记录' — covering the full OKR surface comprehensively.

5 / 5

Completeness

It explicitly answers both 'what' (manage cycles, objectives, KRs, alignments, indicators, progress) and 'when' ('当用户需要查看或创建 OKR、管理目标和关键结果、查看对齐关系时使用'), with concrete trigger phrases and an explicit out-of-scope clause.

5 / 5

Trigger Term Quality

Natural trigger phrases are present ('查看或创建 OKR','管理目标和关键结果','查看对齐关系') but coverage relies on a few phrasings without broader synonyms or user-speak variations.

4 / 5

Distinctiveness Conflict Risk

The narrow OKR niche plus explicit exclusions (待办任务→lark-task, 日程→lark-calendar, 绩效评估) make it highly distinct with minimal conflict risk.

5 / 5

Total

19

/

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.

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

Warning

Total

12

/

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.