Content
78%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is an exemplary token-efficient routing document: tables map scenarios to workflows and tools, concrete commands and paths are named, and publishing risk rules include explicit failure handling. The main gap is progressive disclosure — several referenced files do not resolve within the bundle, and some references nest two levels deep inside tool documentation.
Suggestions
Ship the referenced files (workflows/native-ui-cards.md, the profiler's references/video-dna-framework.md and note-dna-framework.md) in the bundle, or remove/directly inline their key content so no referenced path dangles.
Promote the essential content of the tool-nested references (video/note DNA frameworks) to top-level references/ files so all references from SKILL.md are one level deep.
Add brief validation checkpoints inside the body for the data-review loop (e.g. how to verify dna-meta.json linkage before publishing records) to complement the strong publish-side checks.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense routing guidance carried largely by tables — every line states a workflow trigger, tool command, path convention, hard limit, or responsibility boundary, with zero padding or explanation of concepts Claude already knows. This matches anchor 5 (lean and efficient; every token earns its place); the long 视频全案分工硬边界 paragraph is compressed rules, not verbosity. | 5 / 5 |
Actionability | Concrete executable names are given throughout: shell commands ("douyin-style-profiler", "douyin-engagement", "douyin-publish login"), flags ("--kind", "--account"), paths ("douyin/dna/", "dna-0"), and hard limits ("每 24h ≤ 5 条"). Detailed invocation syntax is deferred to nested tool docs, leaving minor gaps — anchor 4 rather than 5. | 4 / 5 |
Workflow Clarity | The scenario→workflow routing table gives unambiguous dispatch, and risky publish operations carry explicit checkpoints and failure handling ("触发风控立即降级，30 分钟内不重试"; "声明不可用时停止并报告"; shared publish lock serialization). It is not 5 because the per-workflow step sequences themselves are delegated to external workflow files not shown in the body. | 4 / 5 |
Progressive Disclosure | The one bundle reference, "references/api-capabilities.md", is real and clearly signaled with its purpose. However, the body also cites "workflows/native-ui-cards.md" and "douyin-style-profiler 的 references/video-dna-framework.md" / "references/note-dna-framework.md", none of which exist in the actual bundle, and the latter two are nested a level inside a tool's own docs — matching anchor 3 (some structure, references not fully resolvable) rather than 4. | 3 / 5 |
Total | 16 / 20 Passed |