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.
Excellent procedural skill: an executable, bounded check-revise loop with strong validation checkpoints and honest failure handling. The only tightening opportunities are a slightly redundant policy sentence and the unspecified report.json findings format.
Suggestions
Document the shape of findings in report.json (field names for flagged questions and probability) so step 4's 'inspect the flagged questions' is fully executable without runtime discovery.
Merge the redundant claim-preservation sentences in the closing policy paragraphs into one statement.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and directive with no padding or explanations of known concepts, but a few sentences restate an already-implied policy (e.g., 'An unsupported claim is not permission to silently replace the author's intended claim' partially repeats the preceding preservation rule), so it falls just short of lean. | 4 / 5 |
Actionability | Copy-paste-ready commands ('jev-prose check draft.txt --profile general > report.json', 'uv tool install ./packages/jev-prose'), concrete flags, exit-code semantics, and report fields to verify ('ran: true', 'ok: true', 'answered == expected'). Minor gap: the structure of findings inside report.json beyond those verification fields is unspecified, leaving 'inspect the flagged questions' to runtime inspection. | 4 / 5 |
Workflow Clarity | A five-step loop with explicit validation checkpoints (exit-code meanings, ran/ok/answered == expected, exit 2 stops the loop), a bounded retry of three revisions and four checks, a never-end-on-unchecked-rewrite rule, and early-stop conditions for feedback cycling — a textbook validate-fix-retry sequence. | 5 / 5 |
Progressive Disclosure | No bundle files exist and the body references none, so nothing points to missing files. The ~66-line body is well-sectioned (Setup, Bounded loop, closing policies), nothing belongs in a separate file, and single-file organization is appropriate for this scope. | 5 / 5 |
Total | 18 / 20 Passed |