CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lark-minutes

仅当用户或上游配置显式指定 lark-minutes 时使用,相关请求统一交由 lark-meeting 技能处理。

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/lark-minutes/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 is an exemplary minimal redirect: token-efficient, unambiguous, and clearly signaled. The only substantive risks are that it fully delegates without any fallback if the target skill is missing, and that the referenced sibling path was not verifiable in the available bundle.

DimensionReasoningScore

Conciseness

The body is three lean lines — a title, one sentence stating purpose ('本技能只用于兼容旧名称,不直接处理业务'), and one mandatory directive. Every token earns its place with zero padding or explanation of concepts Claude already knows.

5 / 5

Actionability

It gives one unambiguous, concrete instruction with an exact path ('MUST 完整读取 ../lark-meeting/SKILL.md,并按照其中的路由和行动指南执行'). It falls short of 5 because all working instructions are outsourced to the target skill and there is no fallback guidance if the referenced file is absent.

4 / 5

Workflow Clarity

This is a single-task skill whose single action (read the successor skill fully and follow it) is unambiguous; the simple-skill exception applies and no destructive or batch operations are involved, so no validation checkpoints are required.

5 / 5

Progressive Disclosure

The single reference is clearly signaled, bolded, and exactly one level deep. It does not reach 5 because the referenced path ../lark-meeting/SKILL.md could not be verified to exist alongside this skill in the bundle structure, leaving a possible dangling reference.

4 / 5

Total

18

/

20

Passed

Description

57%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 appropriately scoped for a compatibility shim: an explicit trigger condition and a clear delegation target with minimal conflict risk. Its weaknesses are a near-absent capability list and no natural synonyms or variations users might actually say beyond the exact skill name.

Suggestions

Add one concrete capability statement (e.g. 'Delegates all lark-meeting/minute-related requests to the lark-meeting skill') so the 'what' describes action rather than only restriction.

Include natural trigger synonyms users might say beyond the exact name, such as meeting minutes, 飞书妙记, or transcription requests, so the shim still fires on paraphrases of the legacy name.

State the relationship to lark-meeting explicitly (e.g. 'legacy alias for lark-meeting') to make the deliberate overlap self-explanatory and reduce conflict ambiguity.

DimensionReasoningScore

Specificity

The description names its domain (lark-minutes compatibility) and a single minimal action ('统一交由 lark-meeting 技能处理' — delegate to the lark-meeting skill), but lists no concrete capabilities of its own, matching the 'names the domain but actions are minimal or generic' anchor. It does not reach 3 because no concrete user-facing actions are enumerated.

2 / 5

Completeness

Both parts are present: an explicit 'when' ('仅当用户或上游配置显式指定 lark-minutes 时使用' — use only when explicitly specified) and a 'what' (compatibility entry delegating to lark-meeting). It falls short of 5 because the 'what' is thin — it primarily states what it does not do rather than concrete capabilities.

4 / 5

Trigger Term Quality

It contains the relevant keywords 'lark-minutes' and 'lark-meeting' but provides no natural synonyms or variations a user might say (e.g. meeting minutes, 飞书/妙记, transcription), fitting 'some relevant keywords but missing common variations or synonyms'. It is above 2 because the keywords present are specific and on-target rather than generic.

3 / 5

Distinctiveness Conflict Risk

It is scoped to fire only on the exact legacy name and forwards to the correct successor skill, minimizing wrong-trigger risk. It is not 5 because it intentionally overlaps lark-meeting's territory by design, so the boundary depends on the explicit-name restriction holding.

4 / 5

Total

13

/

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: 1 suspicious

Warning

Total

12

/

16

Passed

Repository

larksuite/cli

Path

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