CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

basic-discovery-translational-opportunity-finder

Finds translational opportunities that connect basic-research discoveries to clinically meaningful use cases such as diagnosis, stratification, prognosis, treatment response prediction, monitoring, or therapeutic development. Use this skill when a user wants to turn a mechanism finding, pathway signal, cellular phenotype, experimental observation, or omics discovery into a stronger translational research direction. Always separate mechanistic relevance from translational usability, and never present a basic finding as clinically actionable unless the evidence supports that level.

Quality

79%

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 ./awesome-med-research-skills/Evidence Insight/basic-discovery-translational-opportunity-finder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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-structured, highly actionable instruction-only skill with a clear ordered workflow, explicit validation checkpoints, and a properly wired one-level-deep reference bundle. Its weaknesses are redundancy across the caution sections and overlap between inline output specs and the reference modules, plus one missing worked example.

Suggestions

Consolidate the overlapping caution sections ("Core Function should not", "Hard Rules" 3/7/13/14, "What This Skill Should Not Do", "Quality Standard") into a single rules section to cut repetition and tokens.

Remove the inline Section A-I column-level specifications that duplicate references/output-section-guidance.md, keeping only section-level requirements in the body and delegating formatting detail to the reference.

Add a short worked example of a filled Section C opportunity-map row (one path, one bridge-evidence label) so the required table format is unambiguous.

DimensionReasoningScore

Conciseness

The body is mostly efficient and free of filler, but the same cautions are restated across four overlapping sections ("Core Function should not", Hard Rules 3/7/13/14, "What This Skill Should Not Do", and "Quality Standard"), e.g. never treating mechanism relevance as translational usability appears in all of them. Consolidating these would tighten the file without losing information.

3 / 5

Actionability

The 8-step execution, per-path audit checklists, per-section table column specs (Sections C-F), and verbatim templates (redirect message, check-in prompt, Limited Evidence Mode flag, retrieval fallback label) give directly executable guidance. Minor gaps: no worked example of a filled opportunity table, and Step 2 gives retrieval priorities but no concrete search strategy.

4 / 5

Workflow Clarity

The "8 Steps (always run in order)" sequence includes explicit checkpoints (Step 1.5 scope check-in, Step 8 pre-finalize self-review, Section I risk review, retrieval fallback) plus a 15-rule hard checklist. It falls short of 5 because there is no explicit error-recovery loop stating what to revise and re-check if Step 8's review finds a problem.

4 / 5

Progressive Disclosure

All seven references/ files exist, are clearly signaled in the Reference Module Integration section with when-to-use mapping, and are one level deep with no nested references. However, the body duplicates reference content inline (Sections A-I column specs overlap output-section-guidance.md, and Step 3's path list overlaps the use-case framework), which keeps it below the top anchor.

4 / 5

Total

15

/

20

Passed

Description

83%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: it states what the skill does, when to use it with concrete trigger phrases, and behavioral guardrails, all in third person. The only notable gaps are a few missing natural trigger terms and minor overlap risk with closely related sibling skills.

DimensionReasoningScore

Specificity

The description uses third person and enumerates concrete use-case categories ("diagnosis, stratification, prognosis, treatment response prediction, monitoring, or therapeutic development") beyond naming the domain. It falls short of 5 because it rests on a single core action verb ("Finds translational opportunities") rather than multiple distinct concrete actions.

4 / 5

Completeness

It explicitly answers both questions: the first sentence states what the skill does ("Finds translational opportunities that connect basic-research discoveries to clinically meaningful use cases") and "Use this skill when a user wants to turn a mechanism finding... into a stronger translational research direction" gives concrete when-to-use triggers. This matches the top anchor and is above 4 because the when-clause includes specific trigger phrases, not a generic condition.

5 / 5

Trigger Term Quality

Natural domain phrasing is well covered ("mechanism finding, pathway signal, cellular phenotype, experimental observation, or omics discovery", "translational research direction") with synonym variation across input types. A few natural terms researchers would say are missing, such as "biomarker", "drug target", or "bench to bedside".

4 / 5

Distinctiveness Conflict Risk

The translational-opportunity-mapping niche is clearly defined by domain and use-case vocabulary, making wrong-skill triggering unlikely. It sits at 4 rather than 5 because closely related sibling skills named in the body (biomarker-landscape-scanner, drug-target-evidence-landscape) create minor overlap risk for biomarker- or target-evaluation phrasings.

4 / 5

Total

17

/

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/basic-discovery-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.