dingtalk-live

钉钉直播。Use when 用户说直播/我的直播/直播列表。命令前缀：dws live。

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/multi/dingtalk-live/SKILL.md

Quality

Content

70%Weight 40%Scale 1-3

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 for a simple skill: a clean intent table, a single well-signaled reference, and an unambiguous single action. The two areas to tighten are the verbose warning banners (conciseness) and giving at least one ready-to-run example command in the body (actionability).

Suggestions

Condense the experimental and command-availability warning banners into a single short line to reduce token overhead.

Add one copy-paste-ready example in the body, e.g. 'dws live stream list --format json', so the primary action is executable without opening the reference.

Expand the intent table if other live-stream intents exist, so the body covers the full action surface rather than one row.

Dimension	Reasoning	Score
Conciseness	The useful core (intent table + reference link) is lean, but it is padded by two multi-line warning banners plus a prerequisite block, matching 'mostly efficient but could be tightened'; not 3 due to the banner overhead, not 1 because it does not explain concepts Claude already knows.	2 / 3
Actionability	It provides one concrete command ('dws live stream list') and a reference link, but no copy-paste-ready invocation with example flags in the body and the intent table only covers a single row, matching 'some concrete guidance but incomplete'; below 3 because executable detail is offloaded to the reference.	2 / 3
Workflow Clarity	This is a single-action, read-only skill whose one action is unambiguously mapped in the intent table, so per the simple_skills note workflow clarity can score 3 with no validation checkpoints needed; no destructive/batch context to cap it.	3 / 3
Progressive Disclosure	The body points to a real, clearly signaled, one-level-deep reference ('命令参考：[live.md](references/live.md)') that contains the full command usage and example, matching 'clear overview with well-signaled one-level-deep references'.	3 / 3
	Total	10 / 12 Passed

Description

72%Weight 40%Scale 1-3

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 has strong, natural trigger terms and a clear, conflict-resistant niche tied to a specific product and command prefix. Its main weakness is the 'what' side — it names the domain but does not state the concrete actions the skill performs.

Suggestions

After '钉钉直播。', state the concrete capability, e.g. '列出/查看你的钉钉直播列表' so the 'what' is explicit.

Consider adding the primary command inline ('命令前缀：dws live，例如 dws live stream list') to make the action self-evident in the description.

Dimension	Reasoning	Score
Specificity	Names the domain ('钉钉直播') and command prefix ('dws live') but lists no concrete actions (e.g., list/start/query streams), matching the 'names domain and some actions, not comprehensive' anchor; not 3 because no multiple specific concrete actions are listed, not 1 because it is product-specific rather than vague.	2 / 3
Completeness	It has an explicit 'Use when...' trigger (satisfying 'when') but the 'what' is only the domain name ('钉钉直播。') with no described capability, so it does not 'clearly answer both'; not 3 because the what-side is too thin, not 1 because the when-side is explicit.	2 / 3
Trigger Term Quality	'Use when 用户说直播/我的直播/直播列表' covers several natural phrasings a user would say, matching the 'good coverage of natural terms' anchor; above 2 because it lists multiple natural variations rather than a single keyword.	3 / 3
Distinctiveness Conflict Risk	A specific product ('钉钉直播'), distinct command prefix ('dws live'), and narrow triggers ('直播/我的直播/直播列表') give a clear niche unlikely to conflict, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	10 / 12 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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

	Total	13 / 16 Passed

Repository: DingTalk-Real-AI/dingtalk-workspace-cli
Path: skills/multi/dingtalk-live/SKILL.md
Commit: 2c10be2

Reviewed: 9 days 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.