lark-shared

Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling _notice JSON.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced operational guide with strong command-level specificity and validation checkpoints for risky operations. Its weaknesses are mild redundancy in the prose rules and a missed progressive-disclosure opportunity where the existing wiki-token reference is never linked.

Suggestions

Link references/lark-wiki-token-routing.md from the relevant section (e.g., add a 'Wiki token routing: See references/lark-wiki-token-routing.md' pointer) so the bundle file is discoverable rather than orphaned.

Deduplicate repeated guidance — the 'don't show URL then immediately run --device-code' rule and the exit-10 prohibitions each appear multiple times; state each once and reference it.

Consider moving the JSON output contract and/or the high-risk exit-10 approval protocol into reference files so SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly procedural and operational (knowledge Claude lacks) rather than explaining known concepts, but it repeats key rules multiple times — e.g., 'do not show URL then immediately run --device-code' appears twice and the exit-10 prohibitions are restated across several bullets — so it could be tightened.	2 / 3
Actionability	Provides fully executable, copy-paste-ready commands with exact flags ('lark-cli auth login --domain all --no-wait --json', 'LARKSUITE_CLI_NO_UPDATE_NOTIFIER=1 ...', 'lark-cli auth login --device-code <device_code>'), concrete JSON envelopes, and specific fields to read.	3 / 3
Workflow Clarity	Multi-step flows are explicitly sequenced with validation checkpoints — the split-flow first/second round steps, the exit-10 identify→confirm→--yes retry protocol, and the ok==true/exit-code judgment rule — with feedback loops for risky operations via --dry-run and the confirmation gate.	3 / 3
Progressive Disclosure	Sections are clearly headed, but the body is fairly monolithic (JSON contract, high-risk approval protocol, security rules all inline) and the one bundle file references/lark-wiki-token-routing.md is never linked or signaled from SKILL.md, leaving it orphaned.	2 / 3
	Total	10 / 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.

A strong, third-person description with an explicit 'Use for...' trigger and a concrete enumerated list of capabilities. It cleanly answers both what and when and occupies a distinctive niche.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'auth login/status/logout', 'user vs bot identity', 'business-domain permissions (--domain, including all/docs/drive)', 'missing scopes', 'revoking authorization', and 'handling _notice JSON' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Answers both what (specific setup/auth capabilities) and when via the explicit 'Use for lark-cli setup/auth tasks:' trigger guidance, so the 'Use when...' trigger requirement is satisfied.	3 / 3
Trigger Term Quality	Covers natural terms a user would say for this skill ('auth login/status/logout', 'missing scopes', 'revoking authorization') alongside the setup/auth framing, giving good coverage rather than only jargon.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche (lark-cli auth/identity/permissions/_notice) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: larksuite/cli
Path: skills/lark-shared/SKILL.md
Commit: a7865cd

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.