CtrlK
BlogDocsLog inGet started
Tessl Logo

borzoi

Predict genome-wide functional tracks (RNA-seq, CAGE, DNase, ChIP) from DNA sequence with Borzoi. Use this skill when: (1) Scoring the regulatory effect of a variant on expression/accessibility, (2) Generating predicted coverage tracks for a locus, (3) Prioritising non-coding variants by predicted track delta.

64

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

Reviews 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.

DimensionReasoningScore

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

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person, concrete, and concise, with an explicit numbered trigger list covering the skill's three main use cases. The only weakness is slightly incomplete synonym coverage for assay terminology.

DimensionReasoningScore

Specificity

Names multiple concrete actions with named assays — 'Predict genome-wide functional tracks (RNA-seq, CAGE, DNase, ChIP) from DNA sequence', 'Scoring the regulatory effect of a variant on expression/accessibility', 'Generating predicted coverage tracks for a locus', 'Prioritising non-coding variants by predicted track delta' — comprehensive coverage with no generic filler. Not 4, since the action list has no coverage gaps.

5 / 5

Completeness

Explicitly answers both: what ('Predict genome-wide functional tracks... from DNA sequence with Borzoi') and when (a numbered 'Use this skill when' clause with three concrete trigger scenarios). Matches the anchor-5 example structure exactly; the 'when' is fully explicit, so not 4.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('RNA-seq, CAGE, DNase, ChIP', 'regulatory effect', 'expression/accessibility', 'non-coding variants', 'Borzoi'), but common synonyms users would actually say are missing — notably ATAC-seq (the most common accessibility assay) and 'chromatin'. Not 5 because synonym coverage is incomplete; not 3 because the included terms are natural phrases, not just jargon.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Borzoi DNA-to-track prediction) with model- and assay-specific triggers ('Borzoi', 'CAGE', 'predicted track delta') that no generic genomics or annotation skill would claim. Minimal conflict risk; matches anchor 5.

5 / 5

Total

19

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
aipoch/open-science
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.