Content
93%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 lean operational skill: fully executable commands, explicit validation gates before the destructive --confirm step, and well-defined failure/recovery semantics, all within a compact single file. The only minor weakness is that the workflow sequence is conveyed in dense prose rather than an ordered checklist, which keeps workflow clarity just below the top anchor.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~23-line body is dense operational prose with zero padding and no explanations of concepts Claude already knows; every sentence carries a specific rule (file handling, quoting, flags, failure semantics). Matches 'lean and efficient; every token earns its place' — not 4 because nothing can be trimmed without losing operational content. | 5 / 5 |
Actionability | Provides two copy-paste-ready `tiktok-publish publish` commands with full flags, complete invocations of `tiktok-publish check` and `tiktok-publish methods`, and concrete value domains (`public/private/friends`, `on|off`, video-requires-cover). Matches 'fully executable; copy-paste ready commands covering the common cases' — the only placeholders are file paths, which is expected. | 5 / 5 |
Workflow Clarity | A chronological sequence is present (login/export → check → prepare body file → preview → 核对 → --confirm → result file → published-track) with explicit validation checkpoints and error-recovery paths (stop on failure/risk-control/timeout; recorded:false → re-run only ingests; unknown results → no re-send). Not 5 because the sequence is prose-implicit rather than an ordered checklist and a few transitions must be inferred; not 3 because validation for this risky operation is explicit, satisfying the destructive/batch cap. | 4 / 5 |
Progressive Disclosure | The skill is under 50 lines, single-purpose, has no bundle files and needs no external references; content is appropriately placed in a logical paragraph flow (auth → check → command → defaults → confirm → results → failure handling). Per the rubric's simple-skill guideline this qualifies for 5; not 4 because there is nothing that belongs in a separate file at this size. | 5 / 5 |
Total | 19 / 20 Passed |