CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

biogrid-orcs

Accesses BioGRID ORCS CRISPR screen data (organisms, screens, scores). Invoke when user needs to search CRISPR screens, get vocabulary, or retrieve gene scores.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Evidence Insight/biogrid-orcs/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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.

The command documentation and bundle structure are solid — commands are executable and match the packaged script, and the API reference is properly one level deep — but the body is padded with generic template sections that say nothing specific to this skill, and it contains broken cross-references, inconsistent script paths, and a fabricated expected output for its validation step. Cutting the boilerplate and fixing the path/output inconsistencies would substantially improve it.

Suggestions

Remove the generic template sections ('Output Contract', 'Validation and Safety Rules', 'Failure Handling', 'Required Inputs') or rewrite them BioGRID-ORCS-specifically; the Commands, Prerequisites, Usage, and References sections carry all the real content.

Fix the two forward-pointing 'See ## ... above' cross-references and use one consistent script path (e.g. scripts/biogrid_client.py) across all sections.

Replace the fabricated '--help' expected output with the actual argparse usage output, and drop or correct the biogrid_orcs_result.md output convention since the script prints to stdout and writes no file.

DimensionReasoningScore

Conciseness

Roughly half the body is generic template filler ('Use this skill when the request matches its documented task boundary', 'Scope-focused workflow aligned to: <description repeated verbatim>', 'Output Contract', 'Validation and Safety Rules') that adds nothing BioGRID-specific, and Dependencies/Prerequisites and Example Usage/Usage are redundant pairs. Not 1 because there is no concept-explaining padding and the Commands section itself is lean; not 3 because the boilerplate is pervasive rather than occasional.

2 / 5

Actionability

The seven documented commands are concrete, verified against the actual script's arguments, and copy-paste ready with real flags. Not 5 because the script path is inconsistent across sections ('.trae/skills/...' vs 'scripts/...' vs 'cd "20260316/scientific-skills/..."') and the Quick Validation 'Expected output format' block does not match the script's actual behavior.

4 / 5

Workflow Clarity

A sequence exists ('Recommended Workflow' plus per-command guidance) but checkpoints are generic and implicit — 'Run a final validation pass' names no concrete check, and the one concrete validation step (`--help`) documents a fabricated expected output, so it does not function as a real checkpoint. Not 4 because no concrete, correct validation checkpoint is specified; not 2 because the flow is coherent and each command is individually well documented.

3 / 5

Progressive Disclosure

Clear section headers, a real one-level-deep reference (references/api_docs.md) clearly signaled under '## References', and the bulk API detail correctly split out of SKILL.md. Not 5 because the duplicated Dependencies/Prerequisites and Example Usage/Usage sections and the forward-pointing 'See ## Prerequisites above' / 'See ## Usage above' cross-references slightly impair navigation.

4 / 5

Total

13

/

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.

The description is concise, specific, and follows the best-practice pattern of a clear 'what' plus an explicit 'Invoke when...' trigger clause with concrete triggers. It only loses points for minor coverage gaps and missing common synonym terms in the trigger vocabulary.

Suggestions

Add the remaining packaged capabilities as actions, e.g. 'list organisms and search genes by name', to close the specificity gap.

Include common user phrasings like 'CRISPR knockout screens', 'screen hits', or 'gene essentiality scores' in the trigger clause to broaden natural-term coverage.

DimensionReasoningScore

Specificity

Names the niche domain ('BioGRID ORCS CRISPR screen data (organisms, screens, scores)') and several concrete actions ('search CRISPR screens, get vocabulary, or retrieve gene scores'). Not 5 because listing organisms and searching genes by name are packaged commands that are not explicitly named as actions, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ('Accesses BioGRID ORCS CRISPR screen data (organisms, screens, scores)') and when ('Invoke when user needs to search CRISPR screens, get vocabulary, or retrieve gene scores') with concrete trigger phrases, matching the top anchor directly. Not 4 because the when-clause is fully explicit rather than merely present with room for improvement.

5 / 5

Trigger Term Quality

Includes natural phrases users would say such as 'search CRISPR screens', 'get vocabulary', 'retrieve gene scores', and 'BioGRID ORCS'. Not 5 because common variations like 'CRISPR knockout screen', 'screen hits', or 'gene essentiality' are missing.

4 / 5

Distinctiveness Conflict Risk

'BioGRID ORCS' and 'CRISPR screens' carve a clear niche with distinct triggers and third-person voice, so conflict risk with other skills is minimal. Not 4 because the domain and trigger terms are specific enough that overlap with a generic data-access skill is unlikely.

5 / 5

Total

18

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Evidence Insight/biogrid-orcs/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.