Content
82%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.
A lean, command-first skill body that respects the token budget while packing in concrete CLI usage, a clearly sequenced report/build/update workflow with user-confirmation checkpoints, and explicit per-medium dimension checklists including edge-case handling (visual dims marked N/A for text-only samples). Remaining gaps are minor: the update command is not shown, no error-recovery loop is specified, and the dense paragraphs would benefit from section headers.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and dense with operational content only — commands up front, then usage constraints ("统计 scaffold 不能替代 Agent 回读素材后的定性结论", "视频与图文/文字分别建 DNA,不混合样本统计") and dimension checklists, with zero padding or explanations of concepts Claude already knows. It matches anchor 5: every token earns its place. | 5 / 5 |
Actionability | Concrete, executable commands are provided ("kuaishou-style-profiler report --input /绝对路径/样本文字稿.md --sample-id sample-01 --dna-id dna-0 --kind video") along with specific per-stage directives ("记录样本分母、共性、局部借鉴和例外"), and full parameter details are properly deferred to --help. It falls short of anchor 5 because the update command is never shown and some guidance is principle-level rather than executable (e.g. "用户偏好要转译到具体维度"). | 4 / 5 |
Workflow Clarity | The report → build → update sequence is clearly delineated with per-stage deliverables ("report 逐篇描述观测与依据;build 回读全部报告…再完善 DNA 文档与 template"), and there are guardrails/checkpoints such as "DNA 调整经用户确认后写入" and "少量样本不得称为稳定风格". It does not reach anchor 5 because there is no explicit validate→fix→retry feedback loop for error recovery. | 4 / 5 |
Progressive Disclosure | The skill is under 50 lines with no external bundle files needed; full CLI parameters are appropriately deferred to --help and outputs live in a documented default location ("kuaishou/dna/<dna-id>/"), which is good just-in-time structure. It misses anchor 5 because the body has no section headers — commands, usage constraints, workflow, and dimension checklists flow as undifferentiated dense paragraphs, creating minor navigation gaps. | 4 / 5 |
Total | 17 / 20 Passed |