CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lark-workflow-standup-report

日程待办摘要:编排 calendar +agenda 和 task +get-my-tasks,生成指定日期的日程与未完成任务摘要。适用于了解今天/明天/本周的安排。

Quality

80%

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-workflow-standup-report/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 tight, highly actionable workflow document: executable commands for every variant, a concrete output template, and explicit data-processing rules (timestamp conversion, RSVP mapping, conflict detection, ordering). Structure and reference navigation are solid, with only minor trimming opportunities (duplicated ISO 8601 warning) and a little inline detail that duplicates the referenced sibling skills.

DimensionReasoningScore

Conciseness

The body is lean and operational — no concept explanations Claude already knows; every section carries task-specific facts (flag semantics, RSVP mapping, output template). Anchor 4 rather than 5 because the ISO 8601 no-natural-language warning is stated twice (inline comment in Step 1's code block and again in the following blockquote), which could be trimmed to one.

4 / 5

Actionability

Fully executable throughout: exact lark-cli invocations with realistic flag values for each date/filter case (Step 1 and Step 2 code blocks), the expected output fields, a copy-ready markdown output template, and a concrete API-value-to-display-text RSVP mapping table. Matches the 'fully executable; copy-paste ready; common cases covered' anchor.

5 / 5

Workflow Clarity

Three steps are clearly sequenced with a flow diagram, an explicit critical precondition (must read lark-shared for auth), and must-do warnings ('必须显式带上 --complete=false' with the failure mode explained). Read-only reporting, so the destructive/batch validation cap does not apply; anchor 4 rather than 5 because there are no explicit error-recovery checkpoints for failed API calls (delegated implicitly to the shared skill).

4 / 5

Progressive Disclosure

Well-organized sections with a clearly labeled 参考 section pointing one level deep to annotated sibling skills ('必读' for lark-shared, '详细用法' for lark-calendar/lark-task); no bundle directories exist to further split. Anchor 4 rather than 5 because some inline detail (the full +agenda output-field list and RSVP mapping table) overlaps the territory of the referenced lark-calendar skill and could live there.

4 / 5

Total

17

/

20

Passed

Description

75%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 compact, well-targeted description that names the exact subcommands orchestrated, the concrete deliverable (date-scoped schedule plus incomplete-task summary), and an explicit applicability clause covering today/tomorrow/this week. Its main shortfall is that the natural trigger phrases users actually say (early-brief, standup, meeting synonyms) live in the body's 适用场景 rather than in the description where trigger matching happens.

DimensionReasoningScore

Specificity

Names the exact subcommands it orchestrates ('calendar +agenda 和 task +get-my-tasks') and the concrete output (指定日期的日程与未完成任务摘要), matching the 'several specific actions; minor gaps' anchor. Not 3 because the actions are command-level concrete rather than 1-2 generic actions; not 5 because it omits the downstream capabilities (time conversion, conflict detection, sorting) that the body delivers.

4 / 5

Completeness

Explicitly answers what ('编排 calendar +agenda 和 task +get-my-tasks,生成…摘要') and when ('适用于了解今天/明天/本周的安排'). Not 3 because the when-clause is explicit rather than weakly implied; not 5 because the when clause enumerates day-scopes instead of concrete trigger phrases a user would actually say (e.g., the 适用场景 examples in the body).

4 / 5

Trigger Term Quality

Includes natural user terms '今天/明天/本周', '安排', '日程', '待办', '摘要' that users would plausibly say, matching the 'good keyword coverage; a few natural terms missing' anchor. Not 5 because common synonyms surfaced in the body ('早报', '站会/standup', '会议') are absent from the description itself.

4 / 5

Distinctiveness Conflict Risk

The calendar+task orchestration into a standup-style summary is a clear niche with distinct triggers, matching the 'mostly distinct; minor overlap risk' anchor. Minor risk remains of overlapping with the standalone lark-calendar and lark-task skills it references, so not 5.

4 / 5

Total

16

/

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

Warning

Total

12

/

16

Passed

Repository

larksuite/cli

Path

skills/lark-workflow-standup-report/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.