Content
82%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 an exemplary lean, actionable operating contract: concrete CLI commands, explicit fail-closed rules, and clear boundaries with essentially zero wasted tokens. Minor gaps are the un-shown credential-leasing/backfill commands and the lack of a verification step in the batch backfill workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a lean operating contract: every section carries operational rules Claude does not already know (e.g. "Workers return evidence to the gateway. Workers do not post directly.") with no filler, no concept explanations, and no padding. Not 4 because there are no instances of over-explanation that could be trimmed. | 5 / 5 |
Actionability | Concrete, executable commands are given ("jc-slack search '<query>' --channel <channel-name>", "jc-slack reply '<message-permalink>' --text-file <path>") plus exact trigger conditions, event names, and fictional fixtures. Not 5 because the credential-leasing mechanism and backfill procedure are described only in prose without runnable commands; not 3 because the shown commands are complete and executable. | 4 / 5 |
Workflow Clarity | The reply flow and ShitRat trigger have clear sequences with explicit checkpoints (approval-bound confirmation command, fail-closed unmapped-channel behavior, delivery receipts, ":white_check_mark:" after the final result). Not 5 because the batch backfill section ("Backfills paginate channel history, expand active threads...") has no verification step; not 3 because the primary workflows do include validation checkpoints. | 4 / 5 |
Progressive Disclosure | A single well-organized file with clear sections (Boundaries, Credentials, Read workflow, ShitRat work trigger, Approval-bound replies, Backfill, Public fixtures) and one-level-deep pointers ("skills/slack-link/SKILL.md", gateway source paths); no bundle files exist to split content into. Not 5 because the body exceeds 50 lines and dense sections like the ShitRat trigger paragraph could arguably live in a separate reference if a bundle existed. | 4 / 5 |
Total | 17 / 20 Passed |