CtrlK
BlogDocsLog inGet started
Tessl Logo

borzoi

Use Borzoi-style regulatory genomics models for sequence-to-expression or variant-effect analysis. Use when the task asks for noncoding variant impact, regulatory sequence design, or expression prediction.

71

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 concise, well-structured orchestration workflow with concrete domain-specific guidance and clear sequencing. Adding explicit validation/feedback steps and one or two executable command examples would raise actionability and workflow clarity.

Suggestions

Add an explicit validation/retry checkpoint (e.g., verify prediction array shapes or sanity-check effect directions before saving artifacts) to strengthen the workflow's feedback loop.

Include one concrete executable snippet for a common case, such as a sample manifest format or a model-route invocation, to push actionability toward copy-paste ready.

Clarify step 3's manifest format (fields/columns expected) so input building is unambiguous without external references.

DimensionReasoningScore

Conciseness

Lean and efficient: a one-line intro, five terse numbered steps, and a closing note with no padding or explanation of concepts Claude already knows, matching the 5 anchor.

5 / 5

Actionability

Concrete specific guidance (named fields to pin, named artifact types, named evidence sources) but no executable commands or code, placing it above the 3 pseudocode anchor yet short of copy-paste-ready 5.

4 / 5

Workflow Clarity

A clear five-step sequence with checkpoints (step 2's setup-vs-run distinction, step 5's evidence comparison), but no explicit validate-fix-retry feedback loop, so it sits at 4 rather than 5.

4 / 5

Progressive Disclosure

Under 50 lines, self-contained with no need for external references, and well-organized into intro, workflow, and closing note, meeting the simple-skill exception for a 5.

5 / 5

Total

18

/

20

Passed

Description

87%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, specific description that clearly states both capability and trigger conditions for a well-scoped niche. Minor room for additional synonym/extension-style trigger terms.

DimensionReasoningScore

Specificity

Lists several concrete analysis types ('sequence-to-expression or variant-effect analysis', 'noncoding variant impact, regulatory sequence design, or expression prediction') with only minor coverage gaps, fitting the 4 anchor rather than the comprehensive 5.

4 / 5

Completeness

Explicitly states what it does ('Use Borzoi-style regulatory genomics models for sequence-to-expression or variant-effect analysis') and when to use it ('Use when the task asks for...'), matching the 5 anchor for both what and when.

5 / 5

Trigger Term Quality

Includes natural domain phrases users would say ('noncoding variant impact', 'regulatory sequence design', 'expression prediction') with good coverage, but lacks some synonym variants expected for a 5.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Borzoi regulatory genomics) with distinct triggers, making overlap with other skills minimal.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
companion-inc/feynman
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.