CtrlK
BlogDocsLog inGet started
Tessl Logo

lark-minutes

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

64

Quality

79%

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

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

An exemplary minimal compatibility shim: ultra-lean, with a single unambiguous redirect step and a clearly signaled one-level reference to the owning skill. The only mild gap is that the guidance is delegation rather than self-contained executable code, which keeps actionability at 4.

DimensionReasoningScore

Conciseness

The body is two lean lines with no padding or restated concepts Claude already knows — '本技能只用于兼容旧名称,不直接处理业务' plus a single MUST directive — so every token earns its place, matching the 'lean and efficient' anchor 5.

5 / 5

Actionability

It gives a concrete, specific directive — MUST read the exact path '../lark-meeting/SKILL.md' and follow its routing/action guide — which is mostly executable guidance, but it is delegation rather than copy-paste code covering common cases, so it sits at anchor 4 rather than 5.

4 / 5

Workflow Clarity

The workflow is a single unambiguous action (read the sibling SKILL.md and follow its guide) with no risky or destructive operation, so the simple-skill exception applies and the single step scores 5.

5 / 5

Progressive Disclosure

It is a clear overview (compatibility entry) with one well-signaled, one-level-deep reference ('../lark-meeting/SKILL.md') and content appropriately kept thin, matching the anchor 5 example of a clear overview with clearly signaled single-level references.

5 / 5

Total

19

/

20

Passed

Description

66%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 well-scoped compatibility-shim description that explicitly states its single delegation action and a precise, gated trigger, keeping conflict risk minimal. It is somewhat thin on action variety and natural-term coverage, which caps specificity and trigger quality at the midpoint.

Suggestions

Add one or two natural trigger phrases users might actually say (e.g. '会议纪要', 'minutes', 'lark minutes') alongside 'lark-minutes' to lift trigger term quality.

Briefly state the concrete outcome of the handoff (e.g. 'creates/queries meeting minutes via lark-meeting') so the 'what' reads as more than a single delegation action.

Consider noting the deprecated/old-name nature in the description itself so users understand why only an explicit mention should activate it.

DimensionReasoningScore

Specificity

It names the domain (lark-minutes compatibility) and one concrete action — '相关请求统一交由 lark-meeting 技能处理' (delegates requests to lark-meeting) — but lists only that single action, matching the '1-2 concrete actions, not comprehensive' anchor rather than the multi-action anchors above.

3 / 5

Completeness

It answers both 'what' (delegate related requests to lark-meeting) and 'when' ('仅当用户或上游配置显式指定 lark-minutes 时使用'), with the trigger fairly explicit, but the 'what' is a thin single action so it falls short of the comprehensive anchor 5.

4 / 5

Trigger Term Quality

The keyword 'lark-minutes' appears as the explicit trigger ('显式指定 lark-minutes'), but no natural synonyms or variations such as 'minutes' or 'meeting minutes' are included, fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The skill is gated to a distinct trigger ('仅当...显式指定 lark-minutes') and explicitly hands off to lark-meeting, giving it a clear niche with minimal conflict risk, matching the anchor 5 example of distinct triggers and minimal overlap.

5 / 5

Total

15

/

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