CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gi-splice

Detect splice donor and acceptor sites in DNA sequences using the Genomic Intelligence G0 BigBird transformer, via the hosted /v1/tasks/splice/predict API. Returns per-position site probabilities and called sites.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/gi-splice/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 strong, lean body that earns its tokens with API-specific gotchas Claude could not know, fully executable commands, and a clear workflow with pre-request validation. The only weak spots are slight redundancy and a missing output-verification step in the workflow.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious, skill-specific facts (length bounds, 15,000 bp context window, strand and token-span gotchas) and explains nothing Claude already knows; minor trimmable redundancy remains (the "Why This Exists" section and the Demo command duplicated from CLI Reference), keeping it just below anchor 5.

4 / 5

Actionability

Copy-paste-ready bash commands with exact paths and flags, the exact endpoint URLs, a concrete key-resolution order, and the literal export command fully cover the common demo, custom-input, and authentication cases, matching anchor 5.

5 / 5

Workflow Clarity

The three-step workflow (Parse → POST → Render) is clearly sequenced with pre-request validation ("The skill rejects either locally before spending a request"), a RuntimeError for missing keys, and 429/rate-limit surfacing; it is not 5 because there is no explicit post-run output-verification step, and not 3 because checkpoints are largely present and the operation is non-destructive.

4 / 5

Progressive Disclosure

With no bundle files present, the ~115-line body is well organized into clearly headed sections, keeps operational detail appropriately inline, and points to the served OpenAPI schema for authoritative depth; minor gaps (the long Gotchas section and API contract note could live in a reference file) keep it below anchor 5.

4 / 5

Total

17

/

20

Passed

Description

70%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 highly specific, third-person description that names concrete actions, the model, and the exact API endpoint, making it strongly distinct from other skills. Its main weakness is the absence of any "Use when…" trigger guidance, which caps completeness, and a few natural synonyms (splicing, GT-AG) are missing.

Suggestions

Append an explicit trigger clause such as "Use when the user asks to predict splice sites, find donors/acceptors, or score sequences for cryptic splice sites" to raise completeness from 3 to 5.

Add one or two natural synonyms users would actually say — e.g. "splicing" or "intron/exon boundaries" — to broaden trigger-term coverage.

Mention the expected input (single-record gene-body FASTA) so the "what" coverage is comprehensive.

DimensionReasoningScore

Specificity

"Detect splice donor and acceptor sites" and "Returns per-position site probabilities and called sites" are several concrete, well-qualified actions with the mechanism named (hosted /v1/tasks/splice/predict API, G0 BigBird transformer), matching anchor 4; not 5 because input format and scope (gene-body FASTA, thresholds) are not covered.

4 / 5

Completeness

The "what" is clear and concrete, but there is no "Use when…" clause or equivalent explicit trigger guidance in the description, which caps completeness at 3 per the judging guidelines; it is not a 4 because the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Natural phrases like "splice donor and acceptor sites" and "DNA sequences" are present, giving good keyword coverage; a few common variations users would say ("splicing", "intron/exon boundary", "GT-AG") are missing, so it falls just short of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The combination of splice-site prediction, the Genomic Intelligence G0 BigBird transformer, and the specific API endpoint carves out a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository

ClawBio/ClawBio

Path

skills/gi-splice/SKILL.md

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.