Agent skill

Biomarker Landscape Scanner

by aipoch in aipoch/medical-research-skills

Scans the biomarker landscape of a disease area by biomarker type, clinical/research use case, evidence layer, validation status, and maturity level.

MITAuto-check passedResearch & Science

Install Biomarker Landscape Scanner

skills CLI
$ npx skills add aipoch/medical-research-skills --skill biomarker-landscape-scanner -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install aipoch/medical-research-skills biomarker-landscape-scanner --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/aipoch/medical-research-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/'awesome-med-research-skills/Evidence Insight/biomarker-landscape-scanner' .claude/skills/biomarker-landscape-scanner && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
biomarker-landscape-scanner
GitHub stars
1.9k
Token cost
~4.9k tokens
SKILL.md length
2,317 words
Files
10 (incl. references)
Skills in repo
578
Repo updated
First seen
Licence
MIT

At a glance

Scans the biomarker landscape of a disease area by biomarker type, clinical/research use case, evidence layer, validation status, and maturity level.

  • Works in 9 steps: Define the Biomarker Question Precisely → 5 — Scope Check Before Full Analysis → Retrieve Biomarker-Focused Literature… → …
  • A user wants a field-level biomarker evidence map rather than a generic literature summary
  • SKILL.md covers Reference Module Integration, Input Validation, Sample Triggers and Core Function, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Biomarker Landscape Scanner is an agent skill from aipoch/medical-research-skills. 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.

Its SKILL.md is about 4.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `eval_report_biomarker-landscape-scanner_result.json`, `references/biomarker-maturity-framework.md` and `references/biomarker-type-taxonomy.md`).

It sits in Research & Science, covering Clinical and healthcare research. The repository describes itself as: Hundreds of agent skills for medical research, including protocol design, data analysis, evidence insights, and academic writing. The licence is MIT.

When your agent uses it

  • A user wants a field-level biomarker evidence map rather than a generic literature summary
  • Tasks that involve Clinical and healthcare research

Example prompts

  • “Use the biomarker-landscape-scanner skill to scan the biomarker landscape of a disease area by biomarker type, clinical/research use case, evidence…”
  • “/biomarker-landscape-scanner”

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Define the Biomarker Question Precisely
  2. 5 — Scope Check Before Full Analysis
  3. Retrieve Biomarker-Focused Literature Before Mapping
  4. Build a Structured Biomarker Inventory
  5. Classify by Type, Specimen, and Use Case
  6. Audit Validation Level and Evidence Strength
  7. Assign Biomarker Maturity Tier Strictly
  8. Detect Inconsistencies, Bottlenecks, and Translation Barriers
  9. Prioritize the Landscape and Perform Self-Critical Review

What it can do on your machine

Read from SKILL.md and the folder at commit 686e09d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Biomarker Landscape Scanner loads about 4.9k tokens when it runs, and up to ~7k if it reads all its reference files. Until then it costs about 115 tokens; SKILL.md has 2,317 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~115
When it runs · the whole SKILL.md, loaded when a task matches
~4.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from aipoch/medical-research-skills at commit 686e09d, republished under its MIT licence (© aipoch). 2,317 words, ~4,943 tokens.

Download SKILL.mdSave it as .claude/skills/biomarker-landscape-scanner/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
biomarker-landscape-scanner
description
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.
license
MIT
author
AIPOCH

Source: https://github.com/aipoch/medical-research-skills

Biomarker Landscape Scanner

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:

  • what biomarkers have already been proposed in a field,
  • how those biomarkers are being used,
  • which specimen / modality classes dominate the field,
  • which biomarkers are still exploratory,
  • which have reached external validation,
  • which are repeatedly reported but still weak for translation,
  • and which biomarker spaces remain under-validated despite strong interest.

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:

  • use case,
  • biomarker type,
  • validation level,
  • maturity level,
  • translation readiness,
  • and major evidence limitations.

Reference Module Integration

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.


Input Validation

Valid input: [disease / condition / phenotype / therapy context] + [request to scan biomarkers / biomarker landscape / validation status / evidence map / biomarker maturity]

Optional additions:

  • target use case (diagnosis / early detection / differential diagnosis / prognosis / treatment response / recurrence / MRD / monitoring / subtype stratification)
  • biomarker class of interest (genomic / transcriptomic / protein / metabolite / imaging / pathology / clinical score / liquid biopsy / multimodal)
  • target population / stage / treatment setting
  • specimen constraints (blood / plasma / serum / tissue / urine / CSF / stool / imaging / digital pathology)
  • translational emphasis (discovery scan vs validation scan vs near-clinical scan)
  • anchor biomarkers or anchor papers

Examples:

  • “Scan the biomarker landscape for immunotherapy response in gastric cancer.”
  • “What biomarkers have been proposed for early diagnosis of pancreatic cancer, and which are actually validated?”
  • “Map blood-based biomarkers in lupus by use case and maturity.”
  • “Give me a biomarker evidence map for sepsis prognosis and risk stratification.”
  • “Which NSCLC biomarkers are promising for immunotherapy response, and which are still overclaimed?”

Out-of-scope — respond with the redirect below and stop:

  • patient-specific diagnosis, prognosis, treatment, or lab interpretation
  • inventing biomarkers or fabricating evidence / validation status
  • ranking biomarkers based only on popularity, citation count, or one-off performance metrics
  • claiming clinical utility from exploratory association alone

“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.”


Sample Triggers

  • “Map biomarker types and maturity levels in Alzheimer’s disease.”
  • “What are the main prognostic biomarkers in hepatocellular carcinoma, and how mature are they?”
  • “Scan CRC liquid biopsy biomarkers by diagnosis, MRD, recurrence, and treatment response.”
  • “Which sepsis biomarkers are repeatedly reported but still not clinically robust?”
  • “Compare tissue vs blood biomarkers in NSCLC immunotherapy response.”

Core Function

This skill should:

  1. define the exact disease and biomarker scope,
  2. retrieve and organize biomarker-focused literature,
  3. build a structured biomarker inventory,
  4. classify biomarkers by type, specimen, and intended use case,
  5. separate single markers, signatures, panels, and composite models,
  6. assign both validation level and maturity level,
  7. identify strong candidates, overclaimed areas, and under-validated spaces,
  8. assess translation readiness and main barriers,
  9. recommend one best-supported next-step direction.

This skill should not:

  • collapse all biomarkers into one undifferentiated list,
  • mix diagnostic, prognostic, predictive, and monitoring claims casually,
  • equate mechanistic relevance with deployable biomarker value,
  • ignore assay burden, comparator quality, or endpoint definition,
  • present a biomarker as mature just because it appears frequently in the literature.

Execution — 8 Steps (always run in order)

Step 1 — Define the Biomarker Question Precisely

Identify and restate:

  • disease / condition / subtype
  • clinical or research context
  • target population / stage / treatment setting
  • target use case(s)
  • modality / specimen constraints
  • whether the user wants a broad field scan or a focused subdomain scan

If the topic is too broad, narrow it before formal mapping. State assumptions explicitly.

Step 1.5 — Scope Check Before Full Analysis

After defining the biomarker question in Step 1, determine whether the input requires a full field scan or a targeted single-biomarker/subdomain analysis:

  • Targeted Mode: If the user asks about one specific biomarker or a focused subdomain, produce Sections A, C (partial), D, H, and I only. Skip full multi-section enumeration.
  • Full Field Mode: If the user asks for a broad landscape scan, proceed with all Sections A–J.

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.

Step 2 — Retrieve Biomarker-Focused Literature Before Mapping

Retrieve literature focused on the disease-biomarker intersection before formal mapping.

Prioritize:

  1. peer-reviewed biomedical literature and major reviews for field structure,
  2. recent original studies for biomarker discovery and validation claims,
  3. guidelines / consensus only when checking whether a biomarker is clinically embedded,
  4. clearly labeled preprints only as non-peer-reviewed supplementary signals.

Literature accuracy rules at retrieval stage:

  • Do not fabricate papers, authors, journals, years, PMIDs, DOIs, trial names, or guideline status.
  • Do not convert vague field memory into citation-like claims.
  • Do not treat unsourced background beliefs as literature-backed findings.
  • If citation certainty is insufficient, label the point as unverified, evidence-limited, or not confidently confirmed.

Do not assign maturity based on title, abstract hype, or keyword frequency alone.

Step 3 — Build a Structured Biomarker Inventory

Extract candidate biomarkers and biomarker systems, including:

  • single molecules,
  • gene / protein / feature signatures,
  • pathology / imaging markers,
  • liquid-biopsy markers,
  • cellular / immune-state markers,
  • composite clinicomolecular models,
  • dynamic or longitudinal biomarkers when explicitly studied.

Normalize naming where appropriate, but do not over-merge biomarkers that differ by assay, specimen, cut-point, or model construction.

Step 4 — Classify by Type, Specimen, and Use Case

For each biomarker or biomarker class, assign:

  • biomarker type / modality,
  • single marker vs signature / panel / model,
  • specimen / source,
  • intended use case,
  • study setting,
  • endpoint context.

Use references/biomarker-type-taxonomy.md and references/use-case-framework.md.

Step 5 — Audit Validation Level and Evidence Strength

For each biomarker or biomarker class, assess:

  • discovery only vs internal validation vs external validation,
  • retrospective vs prospective support,
  • single-center vs multi-center evidence,
  • comparator strength,
  • assay reproducibility / standardization,
  • replication consistency,
  • whether performance metrics are clinically meaningful,
  • whether added value beyond existing standards is shown.

Use references/validation-level-framework.md and references/evidence-strength-audit.md.

Step 6 — Assign Biomarker Maturity Tier Strictly

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.

Step 7 — Detect Inconsistencies, Bottlenecks, and Translation Barriers

Actively look for:

  • contradictory performance reports,
  • unstable signatures across cohorts / platforms,
  • endpoint heterogeneity,
  • cohort bias / spectrum bias,
  • specimen-timing mismatch,
  • inaccessible or high-burden assays,
  • missing comparator benchmarks,
  • lack of implementation-oriented evidence.

Use references/conflict-and-inconsistency-rules.md and references/translation-readiness-rules.md.

Step 8 — Prioritize the Landscape and Perform Self-Critical Review

Before finalizing, identify:

  • crowded exploratory areas,
  • strongest repeatedly supported candidates,
  • under-validated but clinically meaningful niches,
  • overclaimed biomarker spaces,
  • one primary follow-up direction.

Then explicitly check:

  • whether use cases were mixed improperly,
  • whether maturity was overstated,
  • whether signatures from incompatible platforms were compared too casually,
  • whether “popular” was mistaken for “mature,”
  • whether the primary recommendation truly follows from the evidence map.

Mandatory Output Structure

A. Topic Framing

Define:

  • disease / condition / subtype,
  • scan objective,
  • scope boundaries,
  • assumptions made,
  • intended use-case frame.
B. Retrieval and Evidence Audit

Must include:

  • retrieval scope and source types,
  • approximate evidence composition,
  • what was included vs excluded,
  • direct-topic vs adjacent evidence distinction,
  • evidence-density overview by subarea,
  • citation-certainty notes when important claims could not be fully verified.
C. Structured Biomarker Landscape Map

Provide a structured map organized by use case first, then biomarker class.

For each biomarker entry include:

  • biomarker / signature / model name,
  • type / modality,
  • specimen / source,
  • intended use case,
  • evidence summary,
  • validation level,
  • biomarker maturity tier,
  • translation-readiness note,
  • major limitations.
D. Biomarker Maturity Layer Summary

Summarize the field using the strict maturity system from references/biomarker-maturity-framework.md.

At minimum, state:

  • which biomarker areas are mostly Tier 1–2,
  • which have reached Tier 3,
  • whether any area legitimately approaches Tier 4,
  • whether there is any real Tier 5 evidence,
  • where maturity is often overstated.
Show full SKILL.md (916 more words)Show less
E. Inconsistencies, Controversies, and Failure Modes

Summarize:

  • biomarkers with conflicting reports,
  • reasons for non-reproducibility,
  • assay/platform inconsistencies,
  • endpoint-definition problems,
  • transferability concerns,
  • common overclaim patterns.
F. Validation and Translation Readiness Summary

At the field level, state:

  • which biomarker categories are mostly discovery-stage,
  • which have external validation,
  • which remain analytically or operationally weak,
  • what currently blocks translation.
G. Priority Opportunities and Under-Validated Niches

List the most important follow-up opportunities, such as:

  • biomarker classes needing external validation,
  • subtype / population gaps,
  • specimen-comparison gaps,
  • benchmark-comparison gaps,
  • assay-standardization gaps,
  • implementation-readiness gaps.

Recommend one best next-step direction and explain:

  • why this direction is stronger than alternatives,
  • what evidence supports it,
  • what minimum next validation is required,
  • what the main failure risk is.

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."

I. Self-Critical Risk Review

Include:

  • strongest part of the map,
  • most assumption-dependent part,
  • most likely overcalled biomarker area,
  • easiest-to-misread maturity signal,
  • likely reviewer criticism,
  • fallback interpretation if the top direction weakens under stricter validation.
J. Retrieved and Verified References

List the retrieved references used for the scan.

Reference rules:

  • do not fabricate citations, PMIDs, DOIs, trial names, or guideline status,
  • separate peer-reviewed evidence from preprints if both are used,
  • do not overstate any paper beyond what it directly supports,
  • distinguish primary studies, systematic reviews/meta-analyses, and guideline/consensus evidence whenever possible,
  • do not present unsourced field beliefs as literature-backed conclusions,
  • if evidence is thin or citation certainty is limited, say so explicitly.

Strict Biomarker Maturity Table Standard

When assigning maturity, use the following default reporting table logic.

Maturity TierWorking LabelMinimum Evidence StandardWhat It Still Cannot Claim
Tier 1Exploratory signalDiscovery-stage association only; no meaningful independent validationCannot claim robustness, reproducibility, or translational relevance
Tier 2Early validated candidateInternal validation or limited external retrospective support, but evidence remains narrowCannot claim stable generalizability or implementation readiness
Tier 3Repeatedly supported but still translationally incompleteRepeated support across independent cohorts/settings, yet key barriers remainCannot claim near-clinical readiness if assay, comparator, or operational evidence is weak
Tier 4Near-translation candidateStrong multi-cohort support plus practical assay/workflow plausibility and clearer clinical positioningCannot claim routine care adoption without prospective / implementation-grade evidence
Tier 5Clinically embedded / guideline-adjacent biomarkerFormal role in routine workflow, consensus pathway, or guideline-adjacent context clearly supportedCannot 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.


Formatting Expectations

  • Use a map-style output, not a long narrative review.
  • Prefer explicit labels and compact evidence statements.
  • Always distinguish use case, biomarker type, validation level, and maturity tier.
  • Do not merge diagnostic, prognostic, predictive, and monitoring claims into one row unless the evidence genuinely supports multiple roles.
  • When the field is large, group biomarkers into meaningful classes instead of generating a flat exhaustive list.
  • When evidence is uneven, show that unevenness directly instead of smoothing it into a balanced-sounding summary.

Hard Rules

  1. Never present exploratory association as biomarker maturity.
  2. Always separate diagnostic, prognostic, predictive, and monitoring claims.
  3. Always state specimen and assay context when relevant.
  4. Do not treat signatures, panels, and single markers as interchangeable.
  5. Validation level must be assigned separately from maturity tier.
  6. External validation matters more than novelty.
  7. A strong AUROC / C-index in one retrospective cohort is not biomarker maturity.
  8. When evidence conflicts, represent the conflict directly rather than averaging it away.
  9. If guideline / consensus support is absent, do not imply routine clinical adoption.
  10. If the user asks for a broad scan, prioritize structure and evidence hierarchy over completeness theater.
  11. Always include a self-critical review before the primary recommendation.
  12. Never assign Tier 4 or Tier 5 language casually; those tiers require explicit evidence beyond repeated association.
  13. Never fabricate references, PMIDs, DOIs, trial names, or validation claims.
  14. Do not present unsourced field beliefs or vague memory as literature-backed conclusions.
  15. Always distinguish exploratory reports, retrospective validation, external validation, prospective evidence, and clinical implementation evidence.
  16. Do not infer biomarker maturity from popularity, citation volume, or isolated performance metrics alone.
  17. If citation certainty is insufficient, explicitly label the point as unverified or evidence-limited instead of filling the gap.

What This Skill Should Not Do

This skill should not:

  • generate imaginary biomarker opportunities,
  • recommend patient care decisions,
  • force every biomarker into one numerical ranking,
  • confuse biological plausibility with deployable clinical value,
  • hide weak validation behind polished language,
  • pretend a sparse or contradictory field is mature.

Quality Standard

A high-quality output from this skill should read like a decision-useful biomarker evidence map.

The user should come away understanding:

  • which biomarker spaces are crowded,
  • which biomarkers are promising,
  • which are weak, inconsistent, or overclaimed,
  • what level of validation the field has actually reached,
  • what maturity tier different biomarker classes truly deserve,
  • how reliable the literature support is for the main claims,
  • and what the smartest next step would be.

© aipoch, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (references) in awesome-med-research-skills/Evidence Insight/biomarker-landscape-scanner of aipoch/medical-research-skills.

  • SKILL.md
  • eval_report_biomarker-landscape-scanner_result.json
  • references/biomarker-maturity-framework.md
  • references/biomarker-type-taxonomy.md
  • references/conflict-and-inconsistency-rules.md
  • references/evidence-strength-audit.md
  • references/output-section-guidance.md
  • references/translation-readiness-rules.md
  • references/use-case-framework.md
  • references/validation-level-framework.md

Open the folder on GitHubat commit 686e09d

Compare with similar skills

Biomarker Landscape Scanner next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Biomarker Landscape Scanner compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Biomarker Landscape Scanner this skillaipoch/medical-research-skills1.9k—~4.9kAutomated safety check: PassMIT
Clinical Trials Databasegoogle-deepmind/science-skills3.2k2 repos~3.2kAutomated safety check: PassApache-2.0
CHARLS Paper Reproduction Guidexjtulyc/MedgeClaw6171 repos~1.8kAutomated safety check: PassNone
Biomedical Analysis Dispatchxjtulyc/MedgeClaw6171 repos~2kAutomated safety check: PassNone
Research Paperluwill/research-skills862—~1.9kAutomated safety check: PassNone
Research Proposalluwill/research-skills862—~4.5kAutomated safety check: NotesNone

Similar skills

  • Clinical Trials Database

    google-deepmind/science-skills

    Query ClinicalTrials.gov via APIv2. An agent skill from google-deepmind/science-skills.

    3.2k GitHub starsUsed in 2 repos~3.2k tokens
    Research & ScienceAuto-check passed
  • Guides an agent through reproducing papers built on the CHARLS health and retirement survey, from variable mapping to cognition, depression and isolation scores.

    617 GitHub starsUsed in 1 repo~1.8k tokens
    Research & ScienceAuto-check passed
  • Routes bioinformatics, drug discovery, clinical and multi-omics tasks from a chat interface to Claude Code sessions running K-Dense scientific skills, with a live dashboard per task.

    617 GitHub starsUsed in 1 repo~2k tokens
    Research & ScienceAuto-check passed
  • Research Paper

    luwill/research-skills

    A skill your agent uses when the user asks to write or draft an ORIGINAL RESEARCH ARTICLE — IMRaD paper, conference paper, short/workshop paper, 研究论文/期刊论文/会议论文 — reporting their own completed…

    862 GitHub stars~1.9k tokensUpdated today
    Research & ScienceAuto-check passed
  • Research Proposal

    luwill/research-skills

    A skill your agent uses when the user asks to write or draft a PhD / doctoral research proposal, research plan, 研究计划书, or 开题报告 — a forward-looking plan of background, gap, research questions…

    862 GitHub stars~4.5k tokensUpdated today
    Research & ScienceAuto-check: notes
  • Medical Imaging Review

    LeonChaoX/qinyan-academic-skills

    Write comprehensive literature reviews for medical imaging AI research.

    944 GitHub starsUsed in 3 repos~1.1k tokens
    Research & ScienceAuto-check: notes

More from aipoch/medical-research-skills

All 578 skills in this repo
  • Academic Poster Generator

    aipoch/medical-research-skills

    Complete workflow for generating academic research posters from PDF literature; use when you need to extract paper content from PDFs and produce a LaTeX-based poster…

    1.9k GitHub stars~2.2k tokensUpdated 24 days ago
    Auto-check passed
  • Diagnostic Study Quality Assessment Quadas

    aipoch/medical-research-skills

    Analyzes clinical diagnostic accuracy studies for bias using the QUADAS-2 tool.

    1.9k GitHub stars~1.4k tokensUpdated 24 days ago
    Auto-check passed
  • Exploratory Data Analysis

    aipoch/medical-research-skills

    Perform comprehensive exploratory data analysis on scientific data files across 200+ file formats.

    1.9k GitHub stars~3.7k tokensUpdated 24 days ago
    Auto-check passed
  • Iso Certification

    aipoch/medical-research-skills

    A toolkit for preparing ISO 13485:2016 certification documentation for medical device QMS.

    1.9k GitHub stars~1.8k tokensUpdated 24 days ago
    Auto-check passed
  • Journal Skills

    aipoch/medical-research-skills

    Recommends target journals for manuscript submission by analyzing the paper topic/abstract and the journal distribution of similar PubMed literature; use when users ask for journal…

    1.9k GitHub stars~1.7k tokensUpdated 24 days ago
    Auto-check passed
  • Latex Posters

    aipoch/medical-research-skills

    Creates academic-poster writing packages for LaTeX using beamerposter, tikzposter, or baposter.

    1.9k GitHub stars~1.3k tokensUpdated 24 days ago
    Auto-check passed

Questions about Biomarker Landscape Scanner

What does Biomarker Landscape Scanner do?

Scans the biomarker landscape of a disease area by biomarker type, clinical/research use case, evidence layer, validation status, and maturity level. Biomarker Landscape Scanner is an agent skill from aipoch/medical-research-skills. Scans the biomarker landscape of a disease area by biomarker type, clinical/research use case, evidence layer, validation status, and maturity level.

When should I use Biomarker Landscape Scanner?

Biomarker Landscape Scanner fits situations like: A user wants a field-level biomarker evidence map rather than a generic literature summary; tasks that involve Clinical and healthcare research.

How do I install Biomarker Landscape Scanner in Claude Code?

Run `npx skills add aipoch/medical-research-skills --skill biomarker-landscape-scanner -a claude-code`. Or copy the skill folder (awesome-med-research-skills/Evidence Insight/biomarker-landscape-scanner in aipoch/medical-research-skills) into .claude/skills/biomarker-landscape-scanner in your project. Claude Code loads it when a task matches its description.

How do I install Biomarker Landscape Scanner in Codex?

Run `npx skills add aipoch/medical-research-skills --skill biomarker-landscape-scanner -a codex`. Or copy the skill folder (awesome-med-research-skills/Evidence Insight/biomarker-landscape-scanner in aipoch/medical-research-skills) into .agents/skills/biomarker-landscape-scanner in your project. Codex loads it when a task matches its description.

Can I use Biomarker Landscape Scanner in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aipoch/medical-research-skills --skill biomarker-landscape-scanner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/biomarker-landscape-scanner, .gemini/skills/biomarker-landscape-scanner, .github/skills/biomarker-landscape-scanner and .opencode/skills/biomarker-landscape-scanner in your project.

What does Biomarker Landscape Scanner need to run?

SKILL.md names no scripts, command-line tools or credentials: Biomarker Landscape Scanner is instructions for the agent only.

Does Biomarker Landscape Scanner access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Biomarker Landscape Scanner safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Biomarker Landscape Scanner use?

Biomarker Landscape Scanner is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Biomarker Landscape Scanner use?

About 4.9k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.1k tokens, read only when the agent opens those files.

What are the alternatives to Biomarker Landscape Scanner?

Skills that share tags, products or a category with Biomarker Landscape Scanner: Clinical Trials Database (google-deepmind/science-skills, 3.2k stars), CHARLS Paper Reproduction Guide (xjtulyc/MedgeClaw, 617 stars), Biomedical Analysis Dispatch (xjtulyc/MedgeClaw, 617 stars) and Research Paper (luwill/research-skills, 862 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Biomarker Landscape Scanner?

aipoch (a GitHub organization) maintains it in aipoch/medical-research-skills, which has 1,937 GitHub stars. The repository holds 578 skills in this directory. The repository was last updated on September 17, 2026.

Source: aipoch/medical-research-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.