Content
90%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.
An excellent, dense operational skill: executable commands with real flags, explicit QC gates before interpretation, and a clean section flow with zero filler. The only gaps are a missing error-recovery loop for failed samples and no reference files to offload runner-option and sample-sheet detail.
Suggestions
Add a short feedback loop for QC-gate failures (e.g. what to check/rerun when TSS enrichment or replicate concordance fails) to make the batch workflow self-correcting rather than just gated.
Move the detailed runner/resource-plan flag documentation into a single one-level reference file and link it from the Route section, keeping the top-level commands minimal.
Document or link the expected sample-sheet format (atac_samples.csv columns) so the commands are executable without guessing the input schema.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and imperative throughout — an inputs checklist, routing commands, QC gates, and outputs — with no explanation of concepts Claude already knows and no padding. Every line carries non-obvious domain specifics (flags, output paths, gates), matching the 'every token earns its place' anchor rather than the score-4 'minor trim' anchor. | 5 / 5 |
Actionability | Three fully-flagged, copy-paste-ready commands (preflight, shared epigenomics package, dedicated ATAC runner) plus concrete artifact names ('qc/atacseq_qc_summary.{tsv,json}', 'qc/atacseq_qc_dashboard.html', 'tracks/', 'resources/resource_plan.json') cover the common cases. This meets the 'fully executable; copy-paste ready; covers common cases' anchor, exceeding score 4 which permits minor gaps. | 5 / 5 |
Workflow Clarity | There is a clear sequence (confirm essential inputs → route/preflight → run the appropriate runner → review QC gates → emit outputs) with an explicit checkpoint ('Review before biological interpretation'; 'Do not proceed to differential accessibility if replicate quality or metadata is insufficient'). It stops short of score 5 because there is no fix-and-retry feedback loop for failing samples and the failed-sample handling is only referenced as an output flag. | 4 / 5 |
Progressive Disclosure | Sections are well-organized with no nested references and clearly signaled external script paths, but the body inlines a substantial amount of runner-flag and resource-plan documentation that would fit a one-level-deep reference file, and details like the sample-sheet format are never linked. This matches the 'good structure; most content appropriately placed; minor organization gaps' anchor rather than the fully split score-5 structure. | 4 / 5 |
Total | 18 / 20 Passed |