Content
42%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 contains a viable workflow with input validation and an executable R command, but it is buried in generic template boilerplate and a fully duplicated nested SKILL document, with conflicting Python-vs-R execution guidance and a Dependencies section that omits the actual R requirements.
Suggestions
Delete the nested `````skill` block (lines 99-224); extract its unique content (parameter descriptions, output template, plot color legend) into properly referenced sections or files instead of duplicating the workflow and data-format table inline.
Resolve the dual entry-point confusion: state one authoritative execution path (the R script), move the Python variant to a clearly labeled fallback section, and update Dependencies to list R plus ggplot2/reshape2 rather than only Python 3.10+.
Remove the template boilerplate ("Key Features" that restates the description, "Deterministic Output Rules", "Completion Checklist") and fix the "Quick Validation" expected output to match what validate_skill.py --check actually prints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | About half the body is boilerplate ("Key Features" restates the description verbatim; "Output Contract", "Deterministic Output Rules", "Completion Checklist" are generic template filler), and the nested `````skill` block (lines 99-224) duplicates the data-format table, domain definitions, and workflow verbatim (~125 lines). Not 1: the data-format spec and R invocation are genuinely necessary content. | 2 / 5 |
Actionability | The command `Rscript scripts/rob2_plot.R "<csv_path>" "<save_name>" "<output_dir>" and the column table are concrete and executable, but the body presents two conflicting entry points (python scripts/rob2_plot.py --help vs. the R script in Step 2), lists only Python 3.10+ under Dependencies while the real workflow needs R with ggplot2/reshape2, and "Quick Validation" promises an expected output validate_skill.py does not produce. Not 4: the authoritative execution path is ambiguous. | 3 / 5 |
Workflow Clarity | A real sequence exists (validate input values -> prompt user to correct -> execute script -> emit formatted summary) and input validation is present, satisfying the batch-validation cap. However, the sequence is undermined by a duplicated nested workflow, an "Example run plan" that points at the Python script instead of the R script, and a dangling "See `## Workflow` above" cross-reference. Not 4: conflicting duplicate guidance obscures the actual sequence and its checkpoints. | 3 / 5 |
Progressive Disclosure | All referenced bundle paths (scripts/rob2_plot.R, scripts/rob2_plot.py, scripts/validate_skill.py) exist and are one level deep, with clear section headers. But a complete second SKILL document is inlined inside a nested fenced block instead of living in a separate file, duplicating ~125 lines of content. Not 2: structure and script references are present and clearly signaled; not 4: the inlined nested document is a major organization gap. | 3 / 5 |
Total | 11 / 20 Passed |