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 well-structured, actionable overview with strong progressive disclosure and concrete commands/paths, though it runs long due to inline platform enumeration and some repeated detail between the intro and 'Current Rules'.
Suggestions
Collapse the inline platform-directory list (e.g. '.claude/, .codex/, .cursor/, ...') into a pointer to references/platform-files/platform-map.md to reduce token cost while keeping platform-specific notes inline.
De-duplicate the bundled-skill name list and workflow-template enumeration, which appear in both the intro paragraph and the 'Current Rules' section — state each once and reference the other.
Add an explicit validate→fix→retry checkpoint in 'How To Use' for editing flows (e.g. after editing, re-read the file and confirm the change against the active workflow template / template-hashes) to lift workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient and free of concept-explanation padding, but the long inline platform-directory enumeration (17+ platforms) and repeated bundled-skill lists in both the intro and 'Current Rules' add length beyond what Claude needs inline. | 3 / 5 |
Actionability | Provides concrete commands ('trellis workflow --template <id>', 'task.py create --parent <slug>', 'trellis mem search|extract|context') and exact paths ('~/.trellis/channels/<project>/<channel>/events.jsonl', '.trellis/.template-hashes.json') plus a precise step-by-step routing sequence to named reference files. | 5 / 5 |
Workflow Clarity | 'How To Use' gives a clear 5-step conditional sequence with an authoritative-source checkpoint (step 5: 'treat local content as authoritative') and a cross-check guard in 'Do Not', but lacks an explicit validate→fix→retry feedback loop for editing operations. | 4 / 5 |
Progressive Disclosure | Clear overview with well-signaled, one-level-deep references organized into three named subsections; all referenced files exist in ./references/ and the body appropriately stays an overview while detail lives in the bundle. | 5 / 5 |
Total | 17 / 20 Passed |