Content
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A concise, well-organized instruction skill with strong domain data and a clear sequenced workflow. Its weaknesses are abstract, non-specific development steps and a terminal validation checklist that lacks explicit error-recovery feedback loops.
Suggestions
Make the development steps more concrete by adding specific methods or criteria, e.g. target navigation depth values, dredge-to-depth specs, or how to identify an obstruction.
Convert the terminal validation checklist into interleaved checkpoints with an explicit feedback loop (e.g. 'if a confluence is undocumented, revisit Course Mapping before proceeding to Channel Improvement').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and well-structured with no padding and no explanation of concepts Claude already knows; every line earns its place. | 3 / 3 |
Actionability | The river-systems list is concrete domain data, but the development steps are abstract instructions ('Locate river origin', 'Trace river path', 'Dredge obstructed sections') that describe rather than give specific concrete methods, so it is not the level-above fully concrete guidance. | 2 / 3 |
Workflow Clarity | A clear five-step sequence with a terminal validation checklist exists, but there are no interleaved checkpoints or explicit 'fix and re-validate' feedback loops; given the batch/destructive nature of channel work this caps the score at 2 per the feedback-loops note. | 2 / 3 |
Progressive Disclosure | Under 50 lines with no external references needed and clearly organized sections (Overview, Major River Systems, Development Steps, Expected Outcomes, Validation), meeting the simple-skills criterion for a top score. | 3 / 3 |
Total | 10 / 12 Passed |