Content
35%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 embeds a formal Lean specification and repeatedly restated governance rules in a monolithic 43KB document, burying a workable round-by-round protocol in redundancy. A reader cannot extract the workflow or produce a concrete round without substantial interpretation; the one reference file is well-signaled but underused.
Suggestions
Move the Lean specification to a file under `references/` and state each governance rule exactly once in SKILL.md — the acceptance and owed-turn rules currently appear six or more times across Definition, FLOW, LOOP, CONVERGENCE, doc comments, Protocol, and Rules.
Add one worked example of a first round (a small task with 3-4 map entries showing relevance, cost-if-wrong, proposals, and the acceptance path) so the abstract round-composition rules have a concrete referent.
Replace the FLOW/LOOP/CONVERGENCE prose commentaries with a single numbered step list that consolidates the standing conditions ("no turn owed", "nothing awaits") as explicit checkpoints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a 43KB monolith in which the same governance rules are heavily padded across many restatements — the acceptance/owed-turn rules appear in "The boundary stands in one of two ways…", the FLOW block, the LOOP commentary ("Neither scan exhaustion nor a visit count constitutes the person's acceptance"), the `AcceptanceSupported` and `owed` doc comments, Protocol bullets, and Rules ("scan exhaustion or a visit count supplies no acceptance"). This is pervasive padding, not the 'several unnecessary sections' of anchor 2, though it is original rather than known-concept explanation. | 1 / 5 |
Actionability | The Protocol section gives round-by-round procedural guidance ("At the first round, show the relevant whole draft before asking the user to choose its applicable parts or examination depth"), but no templates, worked examples, or concrete output formats exist, and the ~550-line Lean block is a formal specification whose axioms are explicitly declared judgments ("a black box to the contract, yours to make"), not executable instructions. Above 2 because the Protocol bullets do give specific sequencing; below 4 because nothing shows what a round or map actually looks like. | 3 / 5 |
Workflow Clarity | A real sequence is present across FLOW and Protocol (first round → present the whole map → rounds serving opened axes and corrections → acceptance or `converge`), and standing conditions ("no turn of the user's is owed", "nothing awaits the person's disposition") function as checkpoints. Below 4 because these steps and checkpoints are scattered through dense prose with no consolidated step list — a reader must parse the entire document to extract the workflow. | 3 / 5 |
Progressive Disclosure | The single bundle reference is real, clearly signaled, and one level deep ("read `references/round-composition.md` before presenting it"), and the body has section headers. Below 4 because the ~550-line Lean specification is inlined wholesale in SKILL.md — content that clearly belongs in a separate reference file — which is a major placement issue rather than a minor organization gap. | 3 / 5 |
Total | 10 / 20 Passed |