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.
The body is highly actionable with real command examples and a strong, sequenced prompt-writing workflow, and is well structured. Its main weakness is repetition: the four-way routing distinction is restated several times, inflating the token budget without adding new information.
Suggestions
Consolidate the device-vs-perception-vs-mic-vs-prompt disambiguation into a single canonical section (e.g. the existing 「何时激活 vs 走别的 skill」/「四路分流」) and cross-reference it from elsewhere instead of restating the rules in 4 places.
Add an explicit post-operation verification step (e.g. re-run scope camera list after mic/disable/prompt changes to confirm the expected in_use/voice_in_use/perception_prompt state) to strengthen feedback loops on batch operations.
Tighten the 「工作方式」 section by removing the rationale paragraphs that re-explain opt-in reasoning and SNR positioning already covered in the example commentary.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient and only covers proprietary CLI behavior Claude would not know, but the four-way device-vs-perception-vs-mic-vs-prompt disambiguation is restated across at least four overlapping sections, adding repeated tokens. | 3 / 5 |
Actionability | Fully executable: concrete miloco-cli commands with flags, batch did semantics, and copy-paste-ready examples with realistic JSON envelope responses covering common cases (home switch, camera disable/enable, mic-on/off, prompt-set/clear). | 5 / 5 |
Workflow Clarity | The prompt-writing flow is clearly sequenced with a confirm-before-write checkpoint, append-not-overwrite handling, and a retry/adjust loop; the 校验行为 table enumerates validation rules, but no explicit post-operation verification step is required beyond backend rejection. | 4 / 5 |
Progressive Disclosure | Well-organized into logical sections with clear headers and no external bundle files needed at this size; minor gaps are the inlined repetition of the disambiguation guidance that could be consolidated, but overall navigation is easy. | 4 / 5 |
Total | 16 / 20 Passed |