Content
81%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 highly actionable with a clearly sequenced, validation-rich workflow and concrete CLI commands. Its main weakness is verbosity from repeated passages and a monolithic structure that leans heavily on inline detail rather than progressive file splits.
Suggestions
Deduplicate the awaiting_sources no-op explanation (currently restated in 'Build and submit the blueprint' and 'Finish, recover, and report') into a single canonical passage and reference it.
Consolidate the repeated 'never create a replacement run/course' injunctions into one stated rule to reduce token cost.
Move the lengthy CLI/Skill freshness and update-protocol detail into a referenced file (e.g. UPDATES.md) to keep SKILL.md a leaner overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient for a complex governed-CLI workflow, but the awaiting_sources no-op behavior is restated nearly verbatim in two sections and 'never create a replacement run' is repeated several times; these duplications could be tightened without losing clarity. | 3 / 5 |
Actionability | Provides fully executable, copy-paste-ready commands with flags and placeholders throughout — 'personwise version --json', 'personwise --account <alias> course create --input <blueprint.json> --json', 'run wait --run-id <run-id> --timeout-seconds 1800 --json' — covering the common cases concretely. | 5 / 5 |
Workflow Clarity | The workflow is clearly sequenced (readiness → blueprint → sources → checkpoints → review → publish) with explicit validation checkpoints and feedback loops: 'If a source fails ... retry ... if the same error returns, stop', and conflict handling via 'read_current_state' with bounded retry then stop. | 5 / 5 |
Progressive Disclosure | Well-structured with clear section headers and one-level-deep, well-signaled references to real bundle files (assets/bootstrap.sh, assets/bootstrap.ps1), but the doc is largely monolithic with extensive inline protocol detail that could be split into referenced files. | 4 / 5 |
Total | 17 / 20 Passed |