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.
The body is highly actionable and well-structured: executable commands, concrete input examples, a sequenced validated workflow, and a best-practice navigation table for bundle files. Weaknesses are duplicated scope/ROC-time guidance across sections, CLI detail inlined that belongs in references/cli-guide.md, and broken references to a tests/ directory that is absent from the bundle.
Suggestions
Consolidate scope guidance: merge 'When to Use' / 'When Not to Use' into the Input Validation section (or vice versa) and state the '--roc_times always in years' rule once (the Arguments table) instead of three times.
Move the full Arguments table and usage examples into references/cli-guide.md, keeping only a single quick-start command in SKILL.md, since the navigation table already routes CLI details there.
Fix or remove the dangling tests/ references (tests/data/BRCA_*.csv, tests/testthat.R, tests/refresh_example_output.R, tests/output/) — either bundle those files or point the examples at paths that exist.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and table-driven with no concept-explaining padding, but scope guidance is repeated across the Input Validation refusal message, 'When to Use', 'When Not to Use', and the Research Use Notice; the '--roc_times always in years' note is stated three times (Arguments, Methods, Examples); and the bundled-test-data command appears twice in Testing. This is more than the 'minor trimmable instances' of level 4, but not the padded/verbose sections of level 2. | 3 / 5 |
Actionability | Fully executable throughout: copy-paste-ready Rscript invocations with all flags, a complete argument table with types/defaults, concrete CSV snippets for all three input formats, error codes with causes and fixes (including a working dedup snippet), and test commands. Common cases (day-unit follow-up, custom colors, ROC positioning) are all covered. | 5 / 5 |
Workflow Clarity | The 4-step workflow is clearly sequenced with explicit validation up front (Step 1 validates files, colors, timeout, seed, time unit), per-step data checks (sample matching, model gene existence), an error-code table that routes persistent failures to references/troubleshooting.md (a feedback loop), and a Testing section with verification commands. Validation is present for this batch operation, so no cap applies. | 5 / 5 |
Progressive Disclosure | The 'When to Read External Files' table provides exemplary, clearly signaled one-level-deep navigation, and every referenced references/*.md and scripts/*.R file exists. Not 5 because the body repeatedly references tests/data/, tests/testthat.R, tests/refresh_example_output.R, and tests/output/ which do not exist in the bundle, and the inlined full CLI argument/usage sections duplicate the dedicated references/cli-guide.md. Not 3 because references are exceptionally well signaled and most content is appropriately placed. | 4 / 5 |
Total | 17 / 20 Passed |