Content
87%Weight 40%Scale 1-3Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
Highly actionable and concise content with executable commands and clean sectioning, weakened only by the absence of an explicit error-recovery feedback loop for the batch QC/peak-calling pipeline.
Suggestions
Add an explicit validate-then-proceed gate (e.g., 'Only proceed to peak calling after confirming alignment rate, duplicate rate, and FRiP meet thresholds; if not, re-run with adjusted --peak-mode or duplicate policy').
Include a feedback loop for poor replicate concordance or weak enrichment (e.g., 'If replicate concordance fails, regenerate consensus peaks or flag the sample rather than proceeding to differential binding').
Make the resource-readiness check a blocking validation step before execution when reference bundles are missing, rather than advisory by default.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and assumes Claude's competence with no concept padding (no 'what is ChIP-seq' exposition); every line is an actionable input, command, decision point, or output spec, so it is not the level-2 'could be tightened' case. | 3 / 3 |
Actionability | Provides fully executable, copy-paste-ready commands with real flags (e.g., run_chip_cutrun_peaks_qc.py --assay chipseq --target-class tf --peak-mode narrow --bowtie2-index ... --execute) plus concrete emitted file paths, matching the 'fully executable code/commands; copy-paste ready' anchor. | 3 / 3 |
Workflow Clarity | The workflow is sequenced (Essential Inputs -> preflight -> runner/nf-core -> Decision Points -> Outputs) with a confirm-checklist and a QC-metric review checkpoint, but for a batch pipeline there is no explicit validate->fix->retry feedback loop, which caps clarity at 2 per the batch-operations guideline; it is not 1 because the sequence and checkpoints are clearly present. | 2 / 3 |
Progressive Disclosure | The skill is a self-contained, well-sectioned overview (Essential Inputs, Route, Decision Points, Outputs) with no nested or deep bundle references to navigate, so the organization alone earns the top level; it is not 2 because nothing that should be separate is awkwardly inline. | 3 / 3 |
Total | 11 / 12 Passed |