Content
88%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 well-structured, actionable guide: a sequenced six-stage workflow with a real validation gate, executable tool commands, and clear safety boundaries around the destructive adopt step. It is mostly concise and uses external docs for deeper material rather than inlining everything.
Suggestions
Tighten the opening paragraph ('SkillOpt-Sleep is Microsoft's SkillOpt deployment-time companion engine: it reviews...') since the 'When to use' and cycle sections already convey the same information more concretely.
Move the advanced engine config keys (gate_mode, gate_metric, dream_rollouts, recall_k, etc.) into a short referenced section or table so the main flow stays scannable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is largely lean and assumes Claude's competence (tool table, params table, tight hard-rules list), with only minor introductory prose ('SkillOpt-Sleep is Microsoft's SkillOpt deployment-time companion engine...') that could be trimmed, fitting the 'efficient; minor instances of over-explanation' anchor rather than the maximally lean 5. | 4 / 5 |
Actionability | Provides copy-paste-ready commands with realistic arguments ('skillopt_run project=<dir> backend=<codex|claude|...> preferences=...', 'skillopt_adopt project=<dir>'), a full tool-behavior table, a parameters table, and a YAML config patch, covering the common cases fully executably. | 5 / 5 |
Workflow Clarity | The six-stage cycle is clearly sequenced with an explicit validation checkpoint (held-out slice, 'accept only on strict improvement'), a backup-before-adopt live-change boundary, and an 'evidence before adoption' hard rule; the destructive/batch cap does not apply because validation is present. | 5 / 5 |
Progressive Disclosure | No bundle files exist, but the body is well-sectioned with clear headers and a one-level-deep external docs link; advanced engine keys are kept inline only briefly. This fits 'good structure; most content appropriately placed; minor organization gaps' rather than the ideal split-over-files 5. | 4 / 5 |
Total | 18 / 20 Passed |