Content
78%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 strong, highly actionable reference: executable commands, complete config examples, cost-aware usage guidance, and a clear setup-with-verification workflow. Its main weaknesses are the total absence of progressive disclosure (a 437-line monolith with a CLI table and config reference that belong in reference files) and a few trimmable changelog-style or redundant sentences.
Suggestions
Move the CLI command table and the config-reference tables into reference files (e.g. references/cli.md, references/config.md) and keep only the most-used commands inline, turning the SKILL.md into a lean overview with one-level-deep, clearly signaled references.
Delete the changelog-style sentence "This fix addresses edge cases where raw user conclusions containing markup or special characters could corrupt the injected context block" — it describes a past change, not guidance.
Close the loop in troubleshooting entries that currently end at diagnosis (e.g. after the 'Honcho not configured' and 'memory not persisting' checks, state what to run or change if the problem persists, mirroring the verify-style feedback loop the Setup section already has).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense reference material Claude cannot know (cadence/depth/level tables, recall modes, tool semantics), mostly free of generic explanations. Minor over-explanation remains: the changelog-style sentence "This fix addresses edge cases where raw user conclusions containing markup or special characters could corrupt the injected context block" and glosses like "You do not need to configure this -- it is automatic based on session state" could be trimmed. Fits 'efficient; minor instances of over-explanation that could be trimmed' rather than the lean 5. | 4 / 5 |
Actionability | Commands are copy-paste ready throughout ("hermes plugins install honcho", "hermes honcho status", "hermes profile create coder --clone", "hermes honcho sync"), config blocks are complete valid JSON, and tool usage comes with concrete good/bad examples ("Prefers code examples over prose explanations" vs "User seems technical"). Setup, daily usage, and troubleshooting cases are all covered with executable guidance. | 5 / 5 |
Workflow Clarity | Sequences are clear and ordered: install → setup wizard → explicit 'Verify' checkpoint with a connection-testing status command, and a numbered conversation-start escalation (profile → context → reasoning) with cost-aware fallbacks. Not a 5 because several troubleshooting entries end at 'check X' without a recovery loop (e.g. what to do if the connection test fails or memory still doesn't persist after the checks). | 4 / 5 |
Progressive Disclosure | No bundle files exist at all — everything is inlined in a 437-line SKILL.md. Internal section structure is good (so not a 2), but substantial reference material belongs in separate files: the 18-command CLI table and the full config-reference tables are exactly the content anchors describe as 'should be separate is inline'. This matches 'some structure but could be better organized' rather than 'most content appropriately placed'. | 3 / 5 |
Total | 16 / 20 Passed |