Content
80%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.
A tight, well-organized command reference with excellent token efficiency and no bundle bloat. Its gaps are operational: no example invocations of the runner, no quick-start sequence tying commands together, and no verification step around the destructive uninstall path.
Suggestions
Add a minimal quick-start sequence (e.g., install → on <name> → status) so the command list becomes a coherent workflow with an implicit verification step.
Show one example invocation of `bin/agentlas-one` (e.g., `bin/agentlas-one on nova`) so the command syntax is copy-paste executable.
For `uninstall [--purge]`, state a verification step after the restore archive is written (e.g., confirm via `status`) to close the destructive-operation validation gap.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a lean command reference with zero padding and no explanation of concepts Claude already knows; even the guardrail 'Anything not listed here does not exist — do not invent one' earns its tokens by constraining hallucinated commands — matching anchor 5 ('lean and efficient; every token earns its place'). | 5 / 5 |
Actionability | Commands are concrete and real ("status [--runtimes|--drift]", "remember <text>", "orch <sub>") with accurate flags and arguments, but no example invocations of `bin/agentlas-one` are shown and several one-line descriptions (e.g., "seed / memory / curate — the drawer") are too terse to execute confidently — anchor 4 ('mostly executable guidance; concrete commands with minor gaps'). | 4 / 5 |
Workflow Clarity | The commands are listed but no sequence is given (e.g., install before on, or how status verifies the install), and the destructive `uninstall [--purge]` has a safety note (a restore archive is written first) but no verification checkpoint — per the destructive-operation guideline, workflow clarity is capped at 3 even though the core on/off action is unambiguous. | 3 / 5 |
Progressive Disclosure | The body is under 50 lines, has no bundle files, and needs none — a well-organized intro plus a Commands section fully covers the skill; per the simple-skill guideline this matches anchor 5. | 5 / 5 |
Total | 17 / 20 Passed |