CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bioinformatics-translational-opportunity-finder

Identifies translationally meaningful paths for bioinformatics findings by mapping omics or computational discoveries to diagnosis, stratification, prognosis, treatment-response, monitoring, or target-nomination use cases, while auditing bridge evidence, assayability, and validation burden. Use this skill when a user wants to know whether a bioinformatics finding can be framed as a stronger translational topic without overclaiming clinical relevance. Always separate statistical signal from translational value, and never imply clinical utility, targetability, or validation depth without explicit evidence support.

Quality

84%

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

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

An exceptionally actionable, well-sequenced instruction skill with explicit validation checkpoints, verbatim templates, and verified one-level-deep reference modules. Its main weakness is substantial redundancy — the anti-overclaim rules and output-format guidance are repeated across many sections and duplicated against reference files, inflating token cost without adding instruction value.

Suggestions

Consolidate the repeated anti-overclaim rules (Input Validation, Core Function 'should not', Step 2 rules, Hard Rules, 'What This Skill Should Not Do', 'Quality Standard') into the single Hard Rules section, removing near-duplicate restatements — this is the largest token saving.

Slim the Mandatory Output Structure to section names plus one-line purposes and let references/output-section-guidance.md carry the per-section requirements, since it already specifies the A–I formatting standard.

Merge 'Formatting Expectations' into the output-section guidance reference, as both cover the same table-vs-prose and labeling rules.

DimensionReasoningScore

Conciseness

The ~370-line body restates the anti-overclaim rules in at least six places — 'Input Validation' out-of-scope list, 'Core Function should not', Step 2 literature rules, 'Hard Rules' (12 items), 'What This Skill Should Not Do', and 'Quality Standard' — and the Mandatory Output Structure duplicates content in references/output-section-guidance.md. This is noticeably verbose with several redundant/padded sections (2 anchor), not merely in need of tightening (3); it avoids 1 because nothing explains concepts Claude already knows.

2 / 5

Actionability

For an instruction-only skill the guidance is fully executable: copy-paste redirect and clarification-check-in templates, explicit discovery-type and use-case taxonomies, concrete reframing examples ('downgrade "clinical biomarker" to "externally unvalidated candidate"'), and a precise section-by-section A–I output spec. Reference modules cited in steps all exist and contain concrete rules. This matches the 5 anchor with specific examples covering the common cases.

5 / 5

Workflow Clarity

The 8 steps are explicitly ordered ('always run in order') with explicit validation checkpoints: a Step 1.5 framing check-in with a minimum clarification threshold, a Step 8 self-critical review checklist, a retrieval-fallback rule, and a stop-and-redirect for out-of-scope requests. Clear sequence plus explicit checkpoints and feedback loops matches the 5 anchor rather than 4, where checkpoints would be minor.

5 / 5

Progressive Disclosure

All 8 referenced modules exist in references/, are one level deep, and are clearly signaled both in a dedicated 'Reference Module Integration' section with step mappings and inline at each step — good structure overall. It falls short of 5 because content that should live in the separate files is inlined: the ~80-line Mandatory Output Structure duplicates references/output-section-guidance.md, and the 12 Hard Rules largely restate material that could be consolidated.

4 / 5

Total

16

/

20

Passed

Description

88%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 in third-person voice that explicitly answers both what the skill does and when to use it, with comprehensive concrete actions and a built-in anti-overclaiming stance. The only weaknesses are a few missing natural trigger synonyms and minor overlap risk against closely related medical-research skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete, comprehensive actions: 'mapping omics or computational discoveries to diagnosis, stratification, prognosis, treatment-response, monitoring, or target-nomination use cases, while auditing bridge evidence, assayability, and validation burden' plus 'separate statistical signal from translational value'. This matches the 5 anchor (multiple specific concrete actions, comprehensive coverage) rather than 4, which would imply minor coverage gaps.

5 / 5

Completeness

Both 'what' (identifies translational paths, audits evidence/assayability/validation burden) and 'when' are explicitly and concretely answered: 'Use this skill when a user wants to know whether a bioinformatics finding can be framed as a stronger translational topic without overclaiming clinical relevance.' This clearly matches the 5 anchor, not 4 where the 'when' is only weakly specified.

5 / 5

Trigger Term Quality

Good domain-natural keywords are present ('bioinformatics finding', 'omics', 'translational topic', 'clinical relevance'), but common synonyms a user might say — 'translational potential', 'clinical translation', 'translational angle' — are absent, fitting the 4 anchor (good coverage, a few natural terms missing) rather than 5.

4 / 5

Distinctiveness Conflict Risk

The bioinformatics/omics translational-positioning niche is distinct with specific triggers, but phrases like 'clinical relevance' and 'bioinformatics finding' carry minor overlap risk with closely related medical-research skills (the body itself references sibling skills like evidence-level-ranker and biomarker-landscape-scanner), fitting the 4 anchor rather than 5.

4 / 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

awesome-med-research-skills/Evidence Insight/bioinformatics-translational-opportunity-finder/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.