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 exemplar of token-efficient, safety-conscious instruction: concrete commands, hard limits, and explicit stop/no-resend conditions with zero fluff. Its weaknesses are structural — no section organization, and a dangling reference to a 'Live Interaction workflow' that doesn't exist in the bundle, which also weakens the actionability of the main procedure.
Suggestions
Resolve the dangling reference: either add the 'Live Interaction workflow' as a real bundled file with a clearly signaled path, or inline the essential steps so the procedure is self-contained.
Add a short example of obtaining room_id (e.g., the `douyin-hunter live room` invocation and which field of its response to use) so the chat/like commands are fully executable end-to-end.
Add minimal section headers (e.g., 命令 / 限制与确认 / 边界与停止条件) to organize the content and satisfy the well-organized-sections bar for short skills.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~15-line body is lean and information-dense — executable commands, hard limits ("弹幕 ≤200 字，单次点赞 1–20 次"), and stop conditions with no padding and no explanation of concepts Claude already knows. Every token earns its place. | 5 / 5 |
Actionability | Provides copy-paste-ready commands with flags (`douyin-live chat --room-id ... --text`, `douyin-live like --room-id ... --count 1`) plus concrete constraints. Not 5 because "按本包 Live Interaction workflow 执行" references a workflow that has no corresponding file in the bundle, and obtaining room_id via `douyin-hunter live room` is named but never shown. | 4 / 5 |
Workflow Clarity | A usable sequence is present (reuse douyin-login session → get room_id from `douyin-hunter live room` → preview → add --confirm) with explicit checkpoints ("风控立即停止", "结果未知先核实，不能自动重发"). Not 5 because the steps are unnumbered/implicit and the referenced 'Live Interaction workflow' does not exist as a bundled file, leaving a gap in the main procedure. | 4 / 5 |
Progressive Disclosure | The skill is under 50 lines and single-purpose (eligible for 5), but there are no section headers and the sole internal reference — "本包 Live Interaction workflow" — is neither signaled with a path nor backed by an actual file (references/, scripts/, assets/ are absent). Some structure exists via the code block and boundary paragraph, but organization and reference signaling need improvement. | 3 / 5 |
Total | 16 / 20 Passed |