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

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

This is a well-structured, highly actionable instruction-only skill with a clear ordered workflow, validation checkpoints, and well-signaled one-level-deep references that all resolve to real files. Its main weakness is redundancy across the overlapping should/should-not rule sections, which inflates token use without adding guidance.

Suggestions

Consolidate the overlapping guidance in 'Core Function', 'Hard Rules', 'What This Skill Should Not Do', and 'Quality Standard' into a single rules block to remove redundancy.

Trim restatements of the same constraints (e.g., 'never present a basic finding as clinically actionable' appears in multiple sections) to one canonical location.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows, but the same should/should-not guidance is restated across 'Core Function', 'Hard Rules', 'What This Skill Should Not Do', and 'Quality Standard', adding redundancy that could be tightened.	3 / 5
Actionability	For an instruction-only skill it provides highly concrete guidance: an ordered 8-step procedure, a mandatory A–I output structure with explicit per-section table columns, plus concrete handling rules for multi-mechanism inputs, limited-evidence mode, and retrieval fallback.	5 / 5
Workflow Clarity	The 'Execution — 8 Steps (always run in order)' is explicitly sequenced with validation checkpoints (Step 1.5 check-in, Step 8 self-critical review), an out-of-scope redirect-and-stop, and a retrieval fallback, giving clear feedback loops.	5 / 5
Progressive Disclosure	The 'Reference Module Integration' section maps each of the seven one-level-deep references to the exact sections/steps where it applies, and all referenced files exist in references/, giving clear navigation and appropriate content split.	5 / 5
	Total	18 / 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.

The description is specific, trigger-rich, and fully answers both 'what' and 'when' in third person, with a clear niche and an explicit behavioral guardrail. It could be slightly stronger with a few more natural synonym triggers and additional distinct action verbs.

Suggestions

Add a few common natural trigger terms (e.g., 'biomarker', 'drug target', 'clinical translation') to broaden keyword coverage.

Introduce one or two additional distinct action verbs beyond 'Finds'/'connects' to make the capability list read as multiple concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain and enumerates concrete use-case types ("diagnosis, stratification, prognosis, treatment response prediction, monitoring, or therapeutic development") and input types, but the core action verbs are limited ("Finds/connects", "turn into"), so coverage is strong rather than comprehensive.	4 / 5
Completeness	Clearly states what it does ("Finds translational opportunities that connect basic-research discoveries to clinically meaningful use cases") and when to use it ("Use this skill when a user wants to turn a mechanism finding..."), with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural keyword coverage with synonyms ("mechanism finding, pathway signal, cellular phenotype, experimental observation, or omics discovery") tied to an explicit "Use this skill when" clause, though common variations like "biomarker" or "drug target" are absent.	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche (basic-discovery-to-translation mapping) with distinct triggers, but has minor overlap risk with closely related medical-research skills like biomarker or drug-target landscape scanners referenced in the body.	4 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: f5ef65b

Reviewed: ~9 hours ago

Table of Contents

Discovery Implementation Validation

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.