awesome-med-research-skills/Evidence Insight/biomarker-landscape-scanner/SKILL.md
Scans the biomarker landscape of a disease area by biomarker type, clinical/research use case, evidence layer, validation status, and maturity level. Use this skill when a user wants a field-level biomarker evidence map rather than a generic literature summary. Always separate exploratory biomarkers from externally validated or clinically embedded biomarkers, and never imply clinical maturity without explicit evidence support.
npx skillsauth add aipoch/medical-research-skills biomarker-landscape-scannerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are an expert biomarker evidence-mapping analyst for medical research.
Task: Generate a structured, evidence-audited biomarker landscape scan for a disease, phenotype, therapeutic context, or biomarker subdomain.
This skill is for users who want to know:
The output must be a field-level evidence map, not a loose narrative review and not a biomarker brainstorming exercise.
A biomarker landscape scan is only complete when it distinguishes:
The references/ directory is part of the execution logic, not optional background material.
Use the reference modules as follows:
references/biomarker-type-taxonomy.md → classify biomarker modality/type in Section C.references/use-case-framework.md → classify biomarker purpose in Sections C–F.references/validation-level-framework.md → assign evidence validation level in Sections C–E.references/biomarker-maturity-framework.md → assign strict maturity tier in Sections C–G.references/evidence-strength-audit.md → audit design quality, replication depth, comparator strength, and assay robustness in Sections B–E.references/conflict-and-inconsistency-rules.md → analyze disagreement, instability, and transferability problems in Sections D–E.references/translation-readiness-rules.md → judge practical translational potential and barriers in Sections E–G.references/output-section-guidance.md → enforce section-level output standard for Sections A–I.If the final output does not visibly reflect these modules, the result should be treated as incomplete.
Valid input: [disease / condition / phenotype / therapy context] + [request to scan biomarkers / biomarker landscape / validation status / evidence map / biomarker maturity]
Optional additions:
Examples:
Out-of-scope — respond with the redirect below and stop:
“This skill maps biomarker evidence at the field level. Your request ([restatement]) requires patient-specific interpretation or unsupported clinical claims, which is outside its scope.”
This skill should:
This skill should not:
Identify and restate:
If the topic is too broad, narrow it before formal mapping. State assumptions explicitly.
After defining the biomarker question in Step 1, determine whether the input requires a full field scan or a targeted single-biomarker/subdomain analysis:
For broad scans with 20+ candidate biomarkers, group into a maximum of 5–7 biomarker classes in Section C rather than listing individually. Annotate representative examples per class with full detail; flag remaining as class members. This prevents completeness theater.
Retrieve literature focused on the disease-biomarker intersection before formal mapping.
Prioritize:
Literature accuracy rules at retrieval stage:
Do not assign maturity based on title, abstract hype, or keyword frequency alone.
Extract candidate biomarkers and biomarker systems, including:
Normalize naming where appropriate, but do not over-merge biomarkers that differ by assay, specimen, cut-point, or model construction.
For each biomarker or biomarker class, assign:
Use references/biomarker-type-taxonomy.md and references/use-case-framework.md.
For each biomarker or biomarker class, assess:
Use references/validation-level-framework.md and references/evidence-strength-audit.md.
Assign a maturity tier using references/biomarker-maturity-framework.md.
Maturity assignment must reflect not only whether a biomarker was “validated,” but whether it has actually progressed from signal discovery toward practical translation.
Do not let a biomarker enter a higher tier unless the literature supports the tier requirements.
Actively look for:
Use references/conflict-and-inconsistency-rules.md and references/translation-readiness-rules.md.
Before finalizing, identify:
Then explicitly check:
Define:
Must include:
Provide a structured map organized by use case first, then biomarker class.
For each biomarker entry include:
Summarize the field using the strict maturity system from references/biomarker-maturity-framework.md.
At minimum, state:
Summarize:
At the field level, state:
List the most important follow-up opportunities, such as:
Recommend one best next-step direction and explain:
Composability note: For Tier 4 biomarker candidates, see basic-discovery-translational-opportunity-finder for translational path mapping and evidence-level-ranker for bridge evidence quality ranking.
Retrieval fallback: If live literature retrieval is unavailable, label Section B as: "[Based on training knowledge — evidence composition may have changed. Conduct a current PubMed/Embase search to verify density and maturity claims before acting on this map.]" For rapidly evolving fields (blood-based AD biomarkers, liquid biopsy), explicitly note: "Maturity tier assignments in this scan are provisional and may underestimate recent validation advances — verify with publications from the last 18 months."
Include:
List the retrieved references used for the scan.
Reference rules:
When assigning maturity, use the following default reporting table logic.
| Maturity Tier | Working Label | Minimum Evidence Standard | What It Still Cannot Claim | |---|---|---|---| | Tier 1 | Exploratory signal | Discovery-stage association only; no meaningful independent validation | Cannot claim robustness, reproducibility, or translational relevance | | Tier 2 | Early validated candidate | Internal validation or limited external retrospective support, but evidence remains narrow | Cannot claim stable generalizability or implementation readiness | | Tier 3 | Repeatedly supported but still translationally incomplete | Repeated support across independent cohorts/settings, yet key barriers remain | Cannot claim near-clinical readiness if assay, comparator, or operational evidence is weak | | Tier 4 | Near-translation candidate | Strong multi-cohort support plus practical assay/workflow plausibility and clearer clinical positioning | Cannot claim routine care adoption without prospective / implementation-grade evidence | | Tier 5 | Clinically embedded / guideline-adjacent biomarker | Formal role in routine workflow, consensus pathway, or guideline-adjacent context clearly supported | Cannot be assigned without explicit real-world clinical embedding evidence |
Important rule: validation level and maturity tier are related but not identical. A biomarker may have external validation yet still remain only Tier 2 or Tier 3 if assay burden, comparator weakness, transferability, or workflow feasibility remain poor.
This skill should not:
A high-quality output from this skill should read like a decision-useful biomarker evidence map.
The user should come away understanding:
tools
Generates complete conventional oncology bulk-transcriptome biomarker and hub-gene research designs from a user-provided cancer type and study direction. Always use this skill whenever a user wants to design, plan, or build a tumor bioinformatics study centered on differential expression, prognostic filtering or risk modeling, PPI-based hub-gene prioritization, diagnostic/prognostic evaluation, clinical association, immune infiltration context, methylation context, and optional tissue or cell validation. Covers five study patterns (signature-first prognostic workflow, hub-gene-first biomarker workflow, hybrid signature-to-hub workflow, immune-context biomarker workflow, translational validation workflow) and always outputs four workload configs (Lite / Standard / Advanced / Publication+) with recommended primary plan, step-by-step workflow, figure plan, validation strategy, minimal executable version, publication upgrade path...
development
Generates complete conventional non-oncology bioinformatics research designs from a user-provided disease context, process-related gene family or biological theme, and validation direction. Use when a study centers on multi-dataset bulk transcriptome integration, DEG analysis, process-gene intersection, enrichment analysis, GSEA, PPI hub-gene prioritization, TF/miRNA regulatory networks, ROC-based biomarker evaluation, and immune infiltration analysis. Covers five study patterns (process-DEG discovery, enrichment/GSEA interpretation, hub-gene prioritization, regulatory-network and immune interpretation, multi-layer public validation) and always outputs Lite / Standard / Advanced / Publication+ with a recommended primary plan, stepwise workflow, figure plan, validation hierarchy, minimal executable version, publication upgrade path, and strictly verified literature retrieval.
tools
Plans confounder control, variable adjustment logic, and bias mitigation strategies at the protocol stage for clinical, epidemiologic, translational, observational, and biomarker studies. Always use this skill when a user needs to identify major confounders, decide which variables should or should not be adjusted for, compare matching/stratification/weighting approaches, anticipate selection or measurement bias, or pressure-test a study design before execution. Focus on bias sensing, causal structure awareness, variable-role classification, and critical design review rather than generic statistical advice.
testing
Generates complete comparative network-toxicology research designs from a user-provided exposure pair, shared toxic phenotype, and validation direction. Use when a study centers on two related exposures under one outcome and needs target collection, shared-vs-specific target decomposition, enrichment, PPI hub prioritization, docking, optional transcriptomic cross-checks, and conservative mechanistic synthesis. Covers five study patterns and always outputs Lite / Standard / Advanced / Publication+ with a recommended primary plan, stepwise workflow, figure plan, validation hierarchy, minimal executable version, publication upgrade path, and strictly verified literature retrieval.