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.
A dense, highly actionable operational protocol with excellent command-level specificity and a well-gated, validated workflow. Its main weaknesses are noticeable internal repetition and incomplete signaling of the existing bundle reference files.
Suggestions
Remove the duplicated 'show' command block in 'Discovery First' (lines 87-94 repeat commands already given at lines 41-47) and consolidate the MD2WECHAT_API_KEY requirement, which is currently stated four times, into a single bullet.
Split the oversized paragraph in 'Article Workflow' (line 122) into short per-command bullets so the readiness gate and preview semantics are scannable.
Either link the remaining bundle files (e.g., sync/zhihu.md, sync/csdn.md, writing/forms.md, writing/platforms.md) from the relevant Intent Routing bullets, or state that the CLI 'skills read' command is the only entry point so readers know these files are not meant to be opened directly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is operational rather than tutorial, but it repeats itself: the four 'show' discovery commands appear twice verbatim in 'Discovery First' (lines 41-47 and 89-94), and the MD2WECHAT_API_KEY requirement is stated four times across 'Configuration Boundaries' and 'Publishing Side Effects'; the dense paragraph at line 122 could also be split. | 3 / 5 |
Actionability | Every section gives exact, executable commands with flags and JSON output paths ('md2wechat inspect <article.md> --json', 'md2wechat layout validate --file <formatted.md> --json', 'md2wechat title suggest <article.md> --json'), including specific exit semantics like 'PREVIEW_ACTION_REQUIRED returns an empty data.output_file'. | 5 / 5 |
Workflow Clarity | The Article Workflow is a clear numbered sequence gated by an explicit validation checkpoint ('read data.readiness.targets and data.readiness.blockers before deciding whether convert, upload, or draft is blocked'), and Failure Handling defines feedback loops (validate -> inspect -> fix -> re-validate) for the risky upload/draft operations. | 5 / 5 |
Progressive Disclosure | Structure is good and the two workflow references (references/sync/workflow.md, references/writing/workflow.md) exist and are signaled via CLI 'skills read' commands, but the other bundle files (sync/zhihu.md, sync/csdn.md, writing/forms.md, writing/platforms.md, etc.) are never mentioned or navigable from SKILL.md, and navigation relies on CLI commands rather than direct links. | 4 / 5 |
Total | 17 / 20 Passed |