Content
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The content is dense, executable, and well-structured with no filler — a strong example of token-efficient skill writing. The main gap is the absence of explicit validation/verification checkpoints in the remote-compute and variant-scoring workflows.
Suggestions
Add an explicit validation step after job completion, e.g. verify `tracks.npz` exists and check expected shape before calling `save_artifacts`, with a retry-on-failure branch.
For variant scoring, add a brief checkpoint confirming ref/alt windows share the same centring and length before comparing per-track deltas.
Clarify that the notification payload should be inspected for error/status fields before acting on `featured_files`.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence — it never explains what RNA-seq/DNase/ChIP are or how PyTorch works, and every section (prerequisites table, code, troubleshooting) earns its tokens, matching the 'lean and efficient' anchor. | 3 / 3 |
Actionability | Provides copy-paste-ready executable code (`Borzoi.from_pretrained("johahi/borzoi-replicate-0")`), exact tensor shapes `(batch, 4, 524288) → (batch, tracks, 6144)`, and concrete fixes (`importlib.metadata.version("borzoi-pytorch")`, pad/crop to 524288 bp), satisfying 'fully executable code/commands; copy-paste ready'. | 3 / 3 |
Workflow Clarity | The remote-compute flow is sequenced (submit_job → wait_for_notification → save_artifacts → attach_job) but lacks explicit validation checkpoints: it never instructs verifying job status or output existence before consuming `payload["featured_files"]`, and the ref/alt variant-scoring task has no verification step. Per the guideline, missing validation in batch/remote operations caps workflow clarity at 2; not 1 because the sequence is clearly present. | 2 / 3 |
Progressive Disclosure | The body is under 50 lines with no bundle files and is well-organized into Prerequisites, How to run, Output format, Remote compute, and Troubleshooting sections; cross-skill pointers (remote-compute-ssh/modal) are one level deep and clearly signaled, fitting the simple-skills allowance for a 3. | 3 / 3 |
Total | 11 / 12 Passed |