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-structured, highly actionable skill body with excellent executable detail, a validated workflow, and a clean reference routing table. The main defects are broken bundle references (a missing diagnosis-report.md and an entire missing tests/ directory the smoke test depends on) and a small amount of author-facing padding (implementation checklist, duplicated command, version stamp).
Suggestions
Ship the referenced test artifacts (tests/data/expression.csv, tests/data/group.csv, tests/validate_outputs.R) or remove the Testing section's smoke-test command, since the documented validation workflow cannot be executed as bundled.
Delete the "Need conversion audit details" row pointing to references/diagnosis-report.md (file does not exist) — it is author-facing conversion-audit material, not agent guidance.
Trim the Implementation Checklist section and the redundant full-flag smoke-test command (or shorten it to a one-line reference to the Usage block) to recover tokens without losing guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dominated by dense, functional tables (arguments, outputs, errors) with no library tutorials or explanations of concepts Claude already knows. Minor trimmable material remains: the author-facing "Implementation Checklist", a smoke-test command that largely duplicates the Usage command, and a version/date stamp line — inefficiencies that could be cut but do not amount to the unnecessary explanation of the score-3 anchor. | 4 / 5 |
Actionability | Fully executable guidance throughout: a complete Rscript invocation with every CLI flag, an argument table with types and defaults, concrete CSV snippets for both required inputs, an exact output-file manifest, and runnable smoke-test/validation commands. Copy-paste ready and covering the common case, matching the score-5 anchor. | 5 / 5 |
Workflow Clarity | Five clearly sequenced workflow steps with validation at both ends (sample-ID consistency checks in Step 1; validate_outputs.R, expected-output checks, and a reproducibility note at the end) and an explicit error-recovery feedback loop: an error-code table with causes and solutions, plus "IF error persists, READ: references/troubleshooting.md". This matches the explicit-validation-and-feedback-loop anchor. | 5 / 5 |
Progressive Disclosure | Good structure: a situation-based "When to Read External Files" routing table, one-level-deep references (verified: no nested references inside the reference files), and appropriate placement of algorithm/CLI detail in references/. However, two of the six routed paths are dead in the actual bundle — references/diagnosis-report.md does not exist, and the Testing section depends on tests/data/ and tests/validate_outputs.R which are absent — so the organization gaps go slightly beyond minor, keeping this below score 5 while remaining clearly above the midpoint. | 4 / 5 |
Total | 18 / 20 Passed |