Content
81%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.
An unusually dense, highly actionable runbook: exact commands, config keys, flags (which match the bundled script's argparse almost entirely), policies, and a well-sequenced configure-preview-apply-verify flow with strong validation loops. The main costs are token efficiency — duplicated CustomerDB verification rules and inline version pins — and a bundle whose only script is not explicitly linked from the body.
Suggestions
State the CustomerDB runtime rules (sent_once/pending handling, cron/heartbeat exclusion, /payment_success and /club_join registration) once — in the CustomerDB section — and cross-reference them from 生效与验证 instead of repeating them nearly verbatim in both sections.
Collect time-sensitive version requirements (OpenClaw 2026.10.4, dependency list) into a single dedicated requirements note at the top rather than repeating the version inline in the CustomerDB section, so future version bumps touch one place.
Explicitly link the bundled script (e.g., "运行 scripts/apply-awada-config.py（CLI 入口 awada-channel-setup）") so the bundle's script is discoverable and the CLI-to-script mapping is unambiguous.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Wording is telegraphic with no concept explanations and every sentence carrying a project-specific rule, but the CustomerDB acceptance rules (sent_once/pending/cron, /payment_success、/club_join not in commands.json) are repeated nearly verbatim in both "CustomerDB hook 标准配置与验收" and "生效与验证", and time-sensitive version pins ("OpenClaw 2026.10.4", "2026.10.4 外部插件注册...") appear inline twice rather than in a requirements/deprecated section. Not a 4 because the duplication and version repetition go beyond minor trimmable instances. | 3 / 5 |
Actionability | Fully executable throughout: copy-paste CLI invocations ("awada-channel-setup --project-root <项目根> --account-id <账号> --agent-id sales-cs --dry-run"), exact config keys ("plugins.entries.awada.config.customerdb"), env-var precedence chains, concrete commands ("openclaw logs --limit 200 --plain", "journalctl --user -u openclaw-gateway.service -n 100 --no-pager") and exact action names/params ("drive.send", "targets", "fileName", "kind", "caption") covering the common cases. | 5 / 5 |
Workflow Clarity | Clear sequenced flow (配置前 prerequisites → dry-run preview → apply with 0600 backup → post-reload verification → troubleshooting) with explicit validation checkpoints and expected values (customerdb/customerdbHooks/customerdbSetup preview states, "hook blocked / DB init failed" log checks, "sales-cs-enablement check-channel --probe") plus error-recovery loops (401/403 → check key and lane scope; lane ambiguity → fix selection; ownership conflict → report and preserve). This is a config-modifying skill and validation is thorough, so no cap applies. | 5 / 5 |
Progressive Disclosure | Six well-scoped sections with clearly signaled one-level-deep pointers ("AGENTS.md 的 ## Tools 节", "OFB_ENV.md", "<项目根>/awada/README.md 的 CustomerDB 节", "docs/AWADA-CLIENT-TRANSPORT.md", "awada/examples/"). Not a 5 because the bundled script (scripts/apply-awada-config.py) is never referenced by path — the body only names the "awada-channel-setup" CLI — and the dense CustomerDB acceptance and log-troubleshooting detail is fully inlined rather than split out. | 4 / 5 |
Total | 17 / 20 Passed |