CtrlK
BlogDocsLog inGet started
Tessl Logo

lark-cli

Use when the user wants to interact with Lark/Feishu/飞书 in any way — including but not limited to: reading, querying, searching, sending, replying to, forwarding, or downloading Lark/Feishu/飞书 IM messages and chat history; managing group chats; listing, viewing, searching, creating, or editing cloud docs/files, Drive, Markdown, spreadsheets, Base tables, wiki, whiteboards, slides, apps, calendars/events/meeting rooms, contacts/org structure, tasks/todos, approvals, attendance, mail, minutes, VC notes, OKRs, real-time events, or custom Lark CLI skills. Load this skill first to find the right sub-skill.

79

Quality

100%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 exemplar dispatcher: concise, fully actionable with executable commands, a clear load-first-then-route workflow, and clean progressive disclosure that delegates to sub-skills. It avoids explaining Lark concepts Claude already knows and provides a sensible --help fallback for unknown commands.

DimensionReasoningScore

Conciseness

The body is lean and information-dense — a prerequisite note, an intent→skill dispatch table, a few load examples, and a help fallback — with no padding or explanation of concepts Claude already knows. The only slight redundancy is repeating the lark-shared load pattern across examples, which still earns its place.

3 / 3

Actionability

Provides concrete, copy-paste-ready commands: read_skills(skill_names=["lark-shared"]), the explicit intent→skill routing table, and lark-cli --help / lark-cli <command> --help examples — fully executable guidance for a dispatcher skill.

3 / 3

Workflow Clarity

Sequences the routing workflow explicitly: load lark-shared first, find the matching sub-skill in the directory, load it, then proceed. As a single-purpose index skill with no destructive/batch operations, its unambiguous single-action workflow meets the clarity bar.

3 / 3

Progressive Disclosure

Acts as a clear overview that defers detail to sub-skills loaded one level deep via read_skills, with a well-signaled dispatch table and organized sections. No local bundle files exist, and the in-file structure is appropriately split and easy to navigate.

3 / 3

Total

12

/

12

Passed

Description

100%

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 a strong, comprehensive trigger for a dispatcher skill: it states concrete capabilities, uses natural multilingual keywords, and pairs an explicit "Use when" clause with a clear "what." Its only minor weakness is a directive imperative ("Load this skill first...") rather than pure third-person descriptive voice, but it avoids first/second-person framing.

DimensionReasoningScore

Specificity

Lists many concrete actions across numerous Lark domains — "reading, querying, searching, sending, replying to, forwarding, or downloading" messages and "listing, viewing, searching, creating, or editing" docs/spreadsheets/etc. — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what ("interact with Lark/Feishu/飞书 in any way") and when ("Use when the user wants to interact with Lark/Feishu/飞书 in any way"), satisfying the explicit-trigger anchor.

3 / 3

Trigger Term Quality

Covers natural trilingual terms users say ("Lark/Feishu/飞书") plus domain terms like IM messages, chat history, group chats, cloud docs, spreadsheets, calendar, mail, and OKRs, giving broad natural-keyword coverage.

3 / 3

Distinctiveness Conflict Risk

Targets a clearly distinct niche (the Lark/Feishu platform, named trilingually) with product-specific triggers, making conflict with other skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
dtyq/magic
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.