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 a tight, well-structured instruction skill: explicit drilling rules, a concrete termination test, specific per-layer writing requirements, and copy-paste output commands. The remaining gaps are the absence of a worked example demonstrating the descent format and minor executable details in the output step (topic slugification, directory creation).
Suggestions
Add one short worked example (a sample topic drilled three layers, showing the layer name and the crack leading to the next layer) so the '怎么写' requirements are demonstrated, not just described.
Specify how to form the {主题} filename slug, and add a mkdir -p (or existence check) for ~/Documents/notes/ before writing the file so the output step is fully executable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~60-line body is efficient and assumes Claude's competence — no known concepts are explained, and rules are stated tersely ('纵向,不横向——每次下钻必须回答"为什么是这样",不是"还有什么"'). Held at 4 rather than 5 because a few lines are atmospheric rather than instructive: the arrow persona ('一支离弦之箭。射出后只知前进,不知后退') and the dual analogies ('像地质学家追踪地层……像物理学家追问粒子') could be trimmed without losing guidance. | 4 / 5 |
Actionability | Mostly executable guidance: three defined iron rules, explicit layer-count guidance ('浅的话题三层见底,深的七层。你自己判断'), per-layer requirements ('每层有命名——给每一层一个精准的名字,两三个字', '层间有裂缝'), a concrete termination test ('再往下问"为什么",答案要么是同义反复,要么指向上述四类之一'), and copy-paste output commands ('date +%Y%m%dT%H%M%S', the file path pattern). Not level 5: no worked example demonstrating the layer-naming/descent format, and the {主题} filename slug and creation of ~/Documents/notes/ are unspecified. | 4 / 5 |
Workflow Clarity | Clear sequence from drilling logic → method → termination criteria → writing requirements → numbered output steps, with an explicit termination checkpoint ('到底的标志:再往下问"为什么"……'). Not level 5: no validation that the output directory exists or that the note file was written successfully before reporting the path — minor validation gaps consistent with the level-4 anchor. This is not a destructive or batch operation, so no level-3 cap applies. | 4 / 5 |
Progressive Disclosure | A single-purpose skill of ~60 lines with no bundle files (no references/, scripts/, or assets/ exist) and no need for external references; everything is appropriately inlined. Sections are well-organized with distinct roles (你是什么 / 钻的逻辑 / 怎么钻 / 什么算到底 / 怎么写 / 输出), matching the simple-skill exception for a well-organized, self-contained body. | 5 / 5 |
Total | 17 / 20 Passed |