CtrlK
BlogDocsLog inGet started
Tessl Logo

lark-attendance

飞书考勤打卡:查询自己的考勤打卡记录

52

Quality

62%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/lark-attendance/SKILL.md
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 is well-structured and actionable with concrete CLI commands and an appropriate cross-skill reference for shared concerns, scoring strongly on progressive disclosure and actionability. Its main weakness is conciseness, where the auto-fill rule is redundantly restated.

Suggestions

Remove the redundant 注意 blockquote that restates the employee_type/user_ids rule already shown in the table and 填充示例 section.

Add one complete end-to-end example command (e.g., `lark-cli attendance user_tasks query --data '{"user_ids":[]}'`) to make guidance fully copy-paste ready.

Add a brief error-handling note (what to do if the schema shows unexpected fields or the API call fails) to close the workflow validation gap.

DimensionReasoningScore

Conciseness

The body is mostly efficient and free of concept-explanation padding, but the employee_type/user_ids auto-fill rule is restated three times (table, 填充示例, and the 注意 blockquote) and could be tightened, fitting 'mostly efficient but could be tightened'.

3 / 5

Actionability

Concrete, real CLI commands are given (lark-cli schema ..., lark-cli attendance ...) with named resource/method (user_tasks.query) and required scope, but no full copy-paste end-to-end example is provided and the --data JSON uses a '...用户提供的参数' placeholder, leaving minor gaps.

4 / 5

Workflow Clarity

The sequence is clear (read lark-shared → run schema first → call API) with an explicit schema-first checkpoint; the missing error-recovery feedback loop is a minor validation gap, and the readonly query is not subject to the destructive/batch cap.

4 / 5

Progressive Disclosure

This is a short (<50 lines), well-organized skill with a single clearly-signaled one-level-deep reference (CRITICAL link to ../lark-shared/SKILL.md) that appropriately delegates shared auth/permissions, meeting the simple-skill bar for a 5.

5 / 5

Total

16

/

20

Passed

Description

53%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 specific and clearly niched to Feishu attendance clock-in queries, but it lacks an explicit 'Use when...' trigger clause and only states a single action, which caps completeness and specificity at 3. Adding trigger guidance and action synonyms would meaningfully raise the score.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when the user asks to check their Feishu/Lark attendance clock-in records') to lift completeness above 3.

Include trigger-term synonyms and variations (查看/获取/导出, 上下班打卡, 打卡时间) so natural keyword coverage reaches more users.

If the skill supports more than query, list additional concrete actions (e.g., filter by date range) to move specificity beyond a single action.

DimensionReasoningScore

Specificity

Names the domain (飞书考勤打卡) and one concrete action (查询自己的考勤打卡记录), matching the 'domain + 1-2 concrete actions, not comprehensive' anchor; it does not enumerate several actions, so it is not a 4.

3 / 5

Completeness

It clearly states what the skill does (query own attendance clock-in records) but has no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Relevant natural terms are present (飞书, 考勤, 打卡, 查询, 记录) but only a single phrasing is used with no synonyms or variations (e.g., 查看/获取/导出, 上下班打卡), fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

飞书考勤打卡 is a clear niche with distinct triggers and minimal conflict risk, though it could overlap with closely related Feishu attendance skills (补卡/请假/stats), placing it just below a 5.

4 / 5

Total

13

/

20

Passed

Validation

68%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation11 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

description_field

'description' is very short (18 chars), consider making it more detailed

Warning

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

11

/

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.