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 unusually actionable editorial procedure: every pattern has a before/after example, the workflow has explicit validation checkpoints and a feedback loop, and it avoids teaching concepts Claude already knows. Its weaknesses are a broken external reference (elements-of-style.md is absent from the bundle) and repetition of the no-fabrication rule that could be trimmed.
Suggestions
Ship elements-of-style.md with the skill or fix its path (e.g., references/elements-of-style.md): the body points to it in the Clarity and Concision section, but no such file exists in the bundle, so the one progressive-disclosure reference is a dead end.
State the never-invent-facts rule once in 'Your Task' and cut its restatements in sections 2, 5, 6, and Process step 3; the Process step 3 audit question alone re-enforces the constraint.
Consider moving the long-tail patterns (e.g., sections 12, 17, 19, 22) to a patterns reference file with the highest-frequency tells summarized in SKILL.md, so the body reads closer to an overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense payload Claude does not already know (33 patterns with before/after pairs, false-positive guidance), but the never-invent-facts rule is repeated at least five times ('Never invent facts', 'Never invent one to make a sentence sound sourced', 'come from sources or the user, not from the rewrite', the Process step 3 audit question) and the em-dash sample exception is restated three times. This fits the 4 anchor ('minor instances of over-explanation that could be trimmed') rather than 5's 'every token earns its place'. | 4 / 5 |
Actionability | For an instruction-only skill the guidance is fully concrete: all 33 patterns carry verbatim Before/After pairs, section 14 gives an executable final check ('scan it for `—` and `–`. Any hit means the draft isn't done'), and the two audit questions are quoted word-for-word. Specific examples cover the common cases, matching the 5 anchor rather than 4, since no key execution detail is missing. | 5 / 5 |
Workflow Clarity | 'Process and Output' sequences draft, audit, final with explicit validation checkpoints (the two named audit questions and the em/en-dash scan) and a revise-to-address feedback loop, and each invocation mode states exactly what to deliver. This matches the 5 anchor ('clear sequence with explicit validation steps; feedback loops'); 4 would require a missing checkpoint, and none are absent. | 5 / 5 |
Progressive Disclosure | Internal structure is well sectioned and the Strunk reference is clearly signaled with size guidance ('~30,000 tokens. Read it only when you are actively writing or editing prose'), but the referenced `elements-of-style.md` does not exist anywhere in the bundle (no references/ directory and no such file in this directory), so the single external reference is a dead end, and the full 33-pattern catalog is inlined in a roughly 450-line body. This fits the 3 anchor ('some structure but could be better organized; content that should be separate is inline') better than 4, whose references must be at least 'mostly clear' with only minor gaps. | 3 / 5 |
Total | 17 / 20 Passed |