Content
65%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.
A well-organized, token-efficient body with genuinely useful specifics (input/output shapes, mouse-head toggle, troubleshooting fixes). Its weakness is that the top advertised use case — variant effect scoring — is described in a single sentence with no executable code and no validation steps, while secondary concerns (remote compute plumbing) get the most detail.
Suggestions
Add an executable variant-scoring snippet to 'How to run': building the (batch, 4, 524288) one-hot ref/alt windows centred on the variant, running both through the model, and computing a per-track delta — currently the primary use case is one prose sentence with no code.
Include a brief validation checkpoint after prediction (e.g., assert output shape is (B, T, 6144) and check job status before reading results), and sequence the variant-scoring workflow as numbered steps so the main flow matches the clarity of the remote-compute section.
Trim the duplicated harness guidance in 'Remote compute' (the suppressed/committed and unread-result sentences) to a pointer to the remote-compute-ssh skill, which the section already cites.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Body is lean — prerequisites table, shapes-in-comments code, and a terse troubleshooting table with no padding — but the remote-compute paragraph inlines convoluted harness guidance ('A final .result() read reports whether its follow-up was suppressed or had already been committed; otherwise the app starts the later analysis turn for an unread final result') that duplicates the remote-compute-ssh skill it already points to. Not 5 because that passage could be trimmed; not 3 because everything else earns its place. | 4 / 5 |
Actionability | Executable code exists for model loading ('Borzoi.from_pretrained(...).cuda().eval()') and job submission, but the skill's primary advertised use case — variant scoring — gets only one prose sentence ('run ref/alt windows centred on the variant and compare per-track output') with no code for building the (batch, 4, 524288) one-hot input or the ref/alt comparison, and the referenced 'borzoi_run.py' is not in the bundle. Key details are missing, matching anchor 3 rather than 4. | 3 / 5 |
Workflow Clarity | The remote-compute flow has a clear sequence (compute_details → create → submitJob → retain job_id → status() → result()), but the core analysis workflow has no step sequence at all and there are no validation checkpoints anywhere (no output-shape check, no job-success check before consuming results). Sequence present with checkpoints missing/implicit matches anchor 3; not 4 because the main-use-case steps are underspecified. | 3 / 5 |
Progressive Disclosure | No bundle files exist, and nothing that belongs in a separate file is inlined — every section is short and belongs in SKILL.md. The single cross-reference (the remote-compute-ssh skill) is one level deep and clearly signaled, and section headers make navigation trivial. Matches anchor 5 for a compact, self-contained skill. | 5 / 5 |
Total | 15 / 20 Passed |