Content
50%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 a densely engineered formal Lean contract that is precise and internally complete, with real verification commands and a genuine one-level reference file. Judged as skill guidance, though, it buries executable steps inside formal notation, offers no plain operational entry point, and inlines nearly all detail in one monolithic block.
Suggestions
Add a short plain-language operational summary (the gate sequence: gather → derive → solution gate → read → sketch → edit → rehearse → hand-off) at the top of the body so the executable workflow can be followed without parsing the Lean state machine.
Move the long grounding strings for the heavier operations (`.read`, `.edit`, `.rehearse`) into `references/` files, keeping one-line summaries inline, to cut the monolithic block down and improve progressive disclosure.
Surface the verification commands (lean-contract.js check, lake build --wfail, lake test, static-checks) as an explicit checklist section rather than leaving them embedded inside the `.edit` string literal.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body contains no padding about concepts Claude already knows, and the prose (Definition, target paragraph) is extremely compressed. However, ~400 lines of dense Lean specification with very long, reference-laden doc strings (e.g. the multi-clause `grounding` strings for `.read` and `.edit`) could be materially tightened or split, matching anchor 3 rather than 4. | 3 / 5 |
Actionability | Concrete, executable commands do appear — "git worktree add --detach <scratch> origin/main", "node .claude/skills/verify/scripts/lean-contract.js generate . && lake build --wfail", "git log -L", "/unfold decide" — but they are embedded inside dense Lean string literals within a formal state machine, and the operational path an executor should follow is never laid out as directly usable guidance. This sits between anchors 3 and 4, landing at 3 for the missing key execution details. | 3 / 5 |
Workflow Clarity | The sequence is fully specified — the FLOW comment, `before` (gather→search→derive→consult; sketch→consult; edit→rehearse), `shows`, and the `run` state machine with gate checkpoints — and the edit operation carries explicit verification commands. But the workflow is expressed in formal Lean semantics and nested bracket conditions rather than a clear ordered procedure, leaving checkpoints implicit for the operational reader; anchor 3 fits better than 4. | 3 / 5 |
Progressive Disclosure | The one bundle reference (`references/reading-checklist.md`) is real, clearly cited inline with a path ("Apply `references/reading-checklist.md` with file:line evidence"), and exactly one level deep. However, the body itself is a near-monolithic 400-line formal block with only two prose sections, and material such as the lengthy grounding strings could arguably live in reference files; anchor 3 (some structure, could be better organized) is the closest fit. | 3 / 5 |
Total | 12 / 20 Passed |