Content
88%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 well-engineered router skill: nearly every line is non-obvious engine contract, the workflow is fully sequenced with validation gates and feedback loops, and detail is appropriately deferred to the manual and two real reference files. The only weaknesses are mild verbosity in policy prose and some contract detail inlined in §2 that could be split out.
Suggestions
Trim the discursive policy sentences (e.g., "No path accepts arbitrary Markdown and returns a finished document: a preset supplies formatting, not missing structure") to bare statements, and tighten the §2 bullet list by moving rarely needed blocked-Markdown cases to a reference file.
Link scripts/reference_layout.py directly from SKILL.md (or from the scenario table in §1) so the DOCX-only paragraph-sample helper is discoverable without reading reference-layout.md first.
The §2 heading/paragraph/equation contract bullets repeat detail also found in the manual (§3.1/§3.4); consider keeping only the decision-level rules inline and pointing to the manual for the exhaustive spellings.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Almost all content is engine-specific contract Claude cannot know (style lines, blocked-Markdown list, gate semantics, exit codes), with no generic concept explanations. A few sentences are discursive policy prose ("No path accepts arbitrary Markdown and returns a finished document: a preset supplies formatting, not missing structure") and parts of the §2 bullet list restate manual detail, keeping it just short of lean. | 4 / 5 |
Actionability | Gives copy-paste-ready commands at every step — `md-to-word --version`, `pip install md-to-word-docx`, `md-to-word manuscript.md -o manuscript.docx`, `md-to-word init`, `md-to-word-template target.docx -o format.txt` — with exact flags, exit codes 0–3, and concrete manuscript syntax examples (`%% Abstract …`, `$$...$$ {#eq-name}`, `[@key]`, `{{< pagebreak >}}`, `{width=13cm}`). | 5 / 5 |
Workflow Clarity | A clear seven-step sequence (scenario → input contract → requirements → export → gates → verify → boundaries) with explicit validation checkpoints: pre-flight validation and a line-by-line audit, the blocking/warning gate split, the feedback loop "Fix the reported line; do not reach for --no-check", and a §6 delivery checklist including --pdf spot-checks. | 5 / 5 |
Progressive Disclosure | The router links references/format-requirements.md and references/reference-layout.md at point of need (both real and substantive, with reference-layout linking scripts/reference_layout.py one level deep) and defers the full vocabulary to the package manual. However, §2 inlines a large block of syntax/blocked-Markdown contract detail that could partly live in a reference file, and scripts/reference_layout.py is never linked directly from SKILL.md. | 4 / 5 |
Total | 18 / 20 Passed |