Content
85%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 excellent executable CLI reference with strong validation discipline around destructive and bulk operations (read-before-write, rev tokens, plan-digest confirmation for site imports). Its main defects are a broken reference to a missing EDITING-FLOW.md and a redundant duplicate explanation of auto-publishing across two sections.
Suggestions
Add the referenced EDITING-FLOW.md to the skill bundle (or inline its essential details on Portable Text conversion, _rev tokens, and raw mode), since the link currently points to a nonexistent file.
Consolidate the auto-publish explanation: state it once, either in 'Content CRUD' or in 'Drafts and Publishing', rather than repeating it in both sections.
Consider moving the long 'Site Export and Import' prose (scope rules, exit codes, principal-mapping semantics) into a reference file to further slim the main SKILL.md once bundle files exist.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense, comment-annotated, copy-paste command blocks with almost no explanation of concepts Claude already knows. Minor redundancy: auto-publish behavior is explained in 'Content CRUD' ('Create and update auto-publish by default so agents get read-after-write consistency') and again in a dedicated 'Drafts and Publishing' section, so it is not a 5; there is no padding or over-explanation that would drop it to 3. | 4 / 5 |
Actionability | Every section provides fully executable commands (e.g., 'npx emdash content create posts --data ...', 'npx emdash site import site.emdash --url ... --analyze') covering the common cases for each command group, including exit codes ('exits 2 when the plan has blockers'), error codes ('INSUFFICIENT_SCOPE'), and required token scopes. This matches 'fully executable; copy-paste ready; specific examples cover the common cases'. | 5 / 5 |
Workflow Clarity | Destructive and bulk operations have explicit validation checkpoints: 'Resolve the current target with a read command before a destructive or bulk mutation', '--rev from a prior get' for updates, and a two-step site import (analyze, review plan and digest, then '--confirm') requiring user confirmation, with failure feedback (exit codes 1/2, status/resume/cancel/abandon). Validation is present, so the destructive-operation cap of 3 does not apply. | 5 / 5 |
Progressive Disclosure | Section structure is good and there is exactly one clearly signaled, one-level-deep reference ('see [EDITING-FLOW.md](./EDITING-FLOW.md)'), but the referenced file does not exist in the bundle, so the reference is broken and the promised detail is unreachable. This is more than the 'minor organization gaps' of a 4, but structure is solid and the reference is not buried, so it is above 2. | 3 / 5 |
Total | 17 / 20 Passed |