Content
75%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 hosting contract: a sequenced eight-step workflow with explicit validation gates, concrete read/write/promote boundaries, and cleanly signaled references. Its main weakness is modest redundancy of the auto-send guard and platform lists across sections.
Suggestions
Collapse the repeated 'never auto-sends/auto-replies/DMs/schedules' guard so it is stated once in the Scope guard and referenced from instruction steps 5 and 7 rather than restated.
State the closed-platform (X/IG/TikTok/LinkedIn/小红书/微信公众号/视频号/抖音) list once in Data Sources and reference it elsewhere to cut duplicated tokens.
Add one copy-paste connector invocation example (e.g. `scripts/connectors/bluesky.py`) to lift actionability toward fully-executable guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is largely efficient and assumes Claude's competence (no definitions of registers, SLAs, or platforms), but the auto-send guard and the closed-platform list are restated across the scope guard, Data Sources, and instruction steps 5/7, which could be trimmed — sitting at efficient-with-minor-redundancy rather than lean. | 4 / 5 |
Actionability | Eight numbered steps give concrete, mostly executable guidance with named scripts (registry-events.py, bluesky.py) and explicit permission-entry fields; it stops short of copy-paste code/invocation examples for the connectors, leaving minor gaps versus the fully-executable score-5 anchor. | 4 / 5 |
Workflow Clarity | A clear eight-step sequence with explicit checkpoints (step 1 NEEDS_INPUT, escalation trip → hand off and stop drafting, idempotent proposals, owner-review flags, a 'Done when' checklist) — the validation is distributed rather than a single validate-then-proceed loop, placing it just below the score-5 anchor. | 4 / 5 |
Progressive Disclosure | Well-organized sections with clearly signaled one-level-deep references (echo-benchmark.md, channel-registry, skill-contract.md, CONNECTORS.md, SECURITY.md) and a dedicated Reference Materials list; with no bundle files present, some inlined detail (repeated platform lists, scope-guard depth) could be externalized, leaving minor organization gaps. | 4 / 5 |
Total | 16 / 20 Passed |