Content
86%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.
A tight, well-structured instruction-only skill: lean prose, deterministic mode routing, a seven-test checklist with remedies, and model bundle separation with conditional read triggers. The two gaps are the absence of any inline worked example showing a test applied to a sentence, and the fact-survival check being stated as a done-condition rather than an explicit verification step in the edit workflow.
Suggestions
Add one short before/after sentence pair to the tests section showing, say, the Mechanism or Portability test applied, so the abstract tests have a concrete anchor without leaving the body.
State the fact check as an explicit step in the edit workflow ("after rewriting, re-check every fact, number, name, and quote against the input before returning") rather than only as a done-condition.
Rewrite the line "Note that the pattern catalog did not apply inside detect findings or inside a change line the caller asked for, and nowhere else" — its double negative makes an exception rule hard to apply correctly on the first read.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~45-line body is lean throughout: no concept Claude already knows is explained, and every rule is operational ("Rewrite only the sentences a test fails on", "One device proves nothing", "Keep exact identifiers, paths, commands, and thresholds"). One sentence — "Note that the pattern catalog did not apply inside detect findings... and nowhere else" — is dense enough to need rereading, but that is a clarity cost, not token waste, so it does not drop below anchor 5's "every token earns its place". | 5 / 5 |
Actionability | The guidance is concrete and directly executable for an instruction-only skill: seven named tests each pair a check with a remedy ("Does the sentence say what the thing does, or how it feels? Replace the feeling with the fact"), mode defaults are deterministic ("no draft means author; an imperative on a draft means edit; a question about a draft means detect"), and boundaries are explicit ("never touch code blocks, quoted text, frontmatter, link targets, identifiers"). It misses anchor 5 because no worked before/after example of a test applied to a sentence appears in the body — examples live entirely in references/patterns.md. | 4 / 5 |
Workflow Clarity | The sequence is clear (determine mode → apply tests → per-mode action → return) and validation exists in three places: the "Done" line is an explicit completion check ("every fact, number, name, quote, and citation in the input survives, and nothing was added"), edit mode carries an idempotency check ("a second pass on the returned text changes nothing"), and detect output format is specified ("Name each pattern found, quote the line, give the fix in a few words"). It falls just short of anchor 5 because fact-survival is stated as an outcome rather than an explicit re-verify step inside the edit workflow, so there is no stated feedback loop of re-checking the output against the input. | 4 / 5 |
Progressive Disclosure | The split is exemplary: the core method (tests, modes, register, boundaries) is inline while the bulk material — a 7.6KB pattern catalog and a terminology guide — lives in references/patterns.md and references/terminology.md, both verified to exist and to deliver what is promised. Each reference is one level deep and cited with a conditional read trigger rather than a bare pointer: "For edit and detect, and for an author passage the tests alone do not settle, read references/patterns.md" and "For wording choices, read references/terminology.md". | 5 / 5 |
Total | 18 / 20 Passed |