Content
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A tight, actionable reference body that respects token budget and points cleanly to external materials; the weakest dimension is workflow_clarity, since the content is a diagnostic lookup guide rather than an ordered workflow with validation checkpoints.
Suggestions
If a canonical debugging workflow exists (e.g. 'phrocs unreachable -> check phrocs.log -> run hogli doctor:report -> restart'), present it as an explicit numbered sequence with a validation/retry checkpoint so workflow_clarity can reach 3.
Add a one-line 'Quick start / first command' pointer near the top so the single most common action (e.g. `hogli --help` or `hogli up -d`) is unambiguously the entry point.
Consider splitting the per-process log details into a short reference table or a referenced file so the overview stays even leaner as the guide grows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence — it covers only non-obvious specifics (where logs land by launch mode, when to prefer MCP over grepping) with no padding about basics, so every token earns its place. | 3 / 3 |
Actionability | Concrete, copy-paste-ready commands and paths throughout ('hogli --help', 'hogli up -d', '.posthog/.generated/logs/', 'hogli doctor:report', 'mcp__phrocs__get_process_logs', 'bin/mprocs.yaml') provide fully executable guidance. | 3 / 3 |
Workflow Clarity | The logging section branches cleanly by launch mode (Detached vs TUI) with a follow-on preference ('prefer mcp__phrocs__get_process_logs'), but it reads as a reference/lookup guide rather than a sequenced multi-step process with explicit validation checkpoints, so it sits at the 'sequence present but checkpoints missing/implicit' anchor rather than a 3. | 2 / 3 |
Progressive Disclosure | A short, single-purpose skill under 50 lines with no bundle files present, organized into clearly signaled sections (Process logging, Key references) and one-level-deep external references; per the simple-skills scoring note this qualifies for a 3 with well-organized sections. | 3 / 3 |
Total | 11 / 12 Passed |