Content
71%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 lean, command-first reference with fully executable invocations and a well-organized structure, undermined by one navigation failure: the constitution.md link is dead, and the validate command's input format is undocumented. Fixing the reference and specifying the graph.json schema would lift it substantially.
Suggestions
Fix the broken reference: constitution.md does not exist in the bundle — either create it with the 6 inviolable rules or remove the Constitution section.
Document the graph.json schema expected by `validate` (inline example or a referenced file), since no format specification exists anywhere in the skill.
Trim the decorative Archimedes epigraph, which adds tokens without operational value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is efficient: commands are presented with minimal prose, the validation passes are a compact table, and credential requirements are stated in two lines without explaining concepts Claude already knows. Minor trimmable elements remain — the Archimedes epigraph is pure decoration and the Synergies section is tangential — fitting anchor 4 ('Efficient; minor instances of over-explanation that could be trimmed') rather than anchor 5's 'every token earns its place'. | 4 / 5 |
Actionability | All three commands are given as full, copy-paste-ready invocations with realistic examples, documented options (--no-bridge, --contradict), and the API-key requirement is explicit. The gap keeping it below 5: the `validate` command's input is never specified — no example graph.json or pointer to its schema exists anywhere in the bundle — so a user cannot actually execute that command end-to-end. This matches anchor 4 ('concrete code or commands with minor gaps'). | 4 / 5 |
Workflow Clarity | Each command is a single unambiguous invocation with examples, and validation is built into the tool itself (the four passes are enumerated), so there are no risky manual multi-step sequences to sequence. However, minor gaps remain: the expected graph.json format for `validate` is undocumented and there is no guidance on interpreting or acting on the engine's output, which fits anchor 4 ('clear sequence with most checkpoints present; minor validation gaps') rather than 5. | 4 / 5 |
Progressive Disclosure | Section structure is good and implementation code is correctly kept in the scripts/ bundle rather than inlined, but the body's only content reference — "See [constitution.md](constitution.md) for 6 inviolable rules" — points to a file that does not exist anywhere in the bundle, and there is no navigation into the actual bundle layout (scripts/toulmin/*.py). This fits anchor 3 ('some structure but could be better organized; references present but not clearly signaled') — the broken reference makes navigation fail at the one place it is attempted. | 3 / 5 |
Total | 15 / 20 Passed |