Agent skill

Bio Longitudinal Monitoring

by GPTomics in GPTomics/bioSkills

Tracks ctDNA across serial liquid-biopsy timepoints for molecular residual disease (MRD) and treatment-response monitoring, treating MRD as a binary integrated detection call across the patient's…

MITAuto-check passedData & Analytics

Install Bio Longitudinal Monitoring

skills CLI
$ npx skills add GPTomics/bioSkills --skill bio-longitudinal-monitoring -a claude-code

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

GitHub CLI
$ gh skill install GPTomics/bioSkills bio-longitudinal-monitoring --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/GPTomics/bioSkills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/liquid-biopsy/longitudinal-monitoring .claude/skills/bio-longitudinal-monitoring && 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
bio-longitudinal-monitoring
GitHub stars
1.2k
Used in
1 other repo
Token cost
~5.1k tokens
SKILL.md length
2,257 words
Files
3
Skills in repo
559
Repo updated
First seen
Licence
MIT

At a glance

Tracks ctDNA across serial liquid-biopsy timepoints for molecular residual disease (MRD) and treatment-response monitoring, treating MRD as a binary integrated detection call across the patient's…

  • Monitoring ctDNA during therapy
  • SKILL.md covers Version Compatibility, The Single Most Important…, Design Decision:… and ctDNA Kinetics Biology -- why…, plus 10 more sections
  • Runs Python scripts from its folder; calls pip
  • Calling molecular relapse before imaging

What it does

Bio Longitudinal Monitoring is an agent skill from GPTomics/bioSkills. Tracks ctDNA across serial liquid-biopsy timepoints for molecular residual disease (MRD) and treatment-response monitoring, treating MRD as a binary integrated detection call across the patient's full variant set (with a defined LoD95 and per-sample specificity) rather than a per-timepoint VAF threshold, and handling undetectable samples as left-censored at the per-sample limit of detection rather than true zeros. Covers tumor-informed bespoke vs tumor-naive design, landmark vs surveillance sampling…

Its SKILL.md is about 5.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `examples/longitudinal_monitoring.py` and `usage-guide.md`).

It sits in Data & Analytics. The repository describes itself as: a set of SKILLS.md for doing bioinformatics with agents like claude code. The licence is MIT.

When your agent uses it

  • Monitoring ctDNA during therapy
  • Calling molecular relapse before imaging
  • Estimating clearance half-life from serial samples

Example prompts

  • “Use the bio-longitudinal-monitoring skill to track ctDNA across serial liquid-biopsy timepoints for molecular residual disease (MRD) and…”
  • “/bio-longitudinal-monitoring”

Requirements

  • Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit d91ed3d. 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

    Ships script files (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • pip

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

  • Network

    No URLs in SKILL.md. Its commands use pip, which can reach the network depending on how they are called.

    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

Bio Longitudinal Monitoring loads about 5.1k tokens when it runs. Until then it costs about 208 tokens; SKILL.md has 2,257 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~208
When it runs · the whole SKILL.md, loaded when a task matches
~5.1k

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 GPTomics/bioSkills at commit d91ed3d, republished under its MIT licence (© GPTomics). 2,257 words, ~5,141 tokens.

Download SKILL.mdSave it as .claude/skills/bio-longitudinal-monitoring/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
bio-longitudinal-monitoring
description
Tracks ctDNA across serial liquid-biopsy timepoints for molecular residual disease (MRD) and treatment-response monitoring, treating MRD as a binary integrated detection call across the patient's full variant set (with a defined LoD95 and per-sample specificity) rather than a per-timepoint VAF threshold, and handling undetectable samples as left-censored at the per-sample limit of detection rather than true zeros. Covers tumor-informed bespoke vs tumor-naive design, landmark vs surveillance sampling, molecular-response definitions and their non-standardization, censoring-aware clearance kinetics, and the multiple-testing structure of repeated surveillance. Use when monitoring ctDNA during therapy, calling molecular relapse before imaging, or estimating clearance half-life from serial samples.
tool_type
python
primary_tool
pandas

Version Compatibility

Reference examples tested with: numpy 1.26+, pandas 2.2+, scipy 1.12+, matplotlib 3.8+

Before using code patterns, verify installed versions match. If versions differ:

  • Python: pip show <package> then help(module.function) to check signatures

If code throws ImportError, AttributeError, or TypeError, introspect the installed package and adapt the example to match the actual API rather than retrying.

Notes specific to this skill: this skill is statistical, not tool-bound. The hard parts are interpretive (left-censoring, multiple testing, lead-time bias), not API calls. scipy.stats.linregress returns a named tuple whose .slope/.pvalue attributes are stable across recent versions; the censoring-aware fit below uses only linregress on the uncensored decay phase plus a manual interval check, so version drift is low-risk.

Longitudinal Monitoring

"Track ctDNA over this course of treatment" -> Integrate serial plasma measurements into a binary detected/not-detected trajectory plus censoring-aware burden kinetics for MRD and response monitoring.

  • Python: pandas for the per-timepoint table, scipy.stats for censoring-aware decay/trend, matplotlib for log-scale trajectory plots

The Single Most Important Modern Insight -- MRD is a binary integrated detection call, and "undetectable" is left-censored, not zero

A tumor-informed MRD assay does not ask "is the VAF at locus X above a threshold?" It integrates signal across the patient's entire personal variant set (16 to 500+ loci) into ONE detected/not-detected call with a defined LoD95 (the tumor fraction detected 95% of the time at a given input) and a per-sample specificity. Signal invisible at any single 0.001%-VAF locus becomes significant when summed across hundreds of loci against a modeled error background; this is why bespoke assays reach 10^-4 to 10^-6 tumor fraction. The detected/not-detected call is the unit of analysis -- per-locus VAF is plumbing, not the readout. Re-deriving a per-timepoint "VAF < X" cutoff throws away the multi-locus integration that makes MRD work and inflates false positives from a single noisy locus.

The second half of the insight: an "undetectable" result is conditional on how many genome-equivalents were interrogated. VAF=0 is LEFT-CENSORED at the per-sample LoD, not a true zero. A 10 mL tube yields roughly 50 ng cfDNA, around 15,000 haploid genome-equivalents; at 0.01% tumor fraction that is roughly 1.5 expected tumor molecules, squarely in the Poisson-limited regime (lambda < 3) where detection is stochastic. "Undetectable" at a low-input draw may simply mean the assay could not have seen the burden it saw at a higher-input draw. Every undetectable must carry its per-sample LoD; plugging 0 into a log-fit or fold-change biases everything and log(0) breaks the fit outright.

Design Decision: tumor-informed vs tumor-naive, landmark vs surveillance

AxisTumor-informed bespokeTumor-naive (fixed panel)
Variant setPatient-specific, designed from tumor/normal WES/WGSFixed gene panel, identical across patients
ExamplesSignatera (16 SNVs, Reinert 2019), RaDaR (up to ~48 amplicons), INVAR (hundreds-thousands of loci, Wan 2020)Broad cfDNA panels, sWGS
MRD sensitivityVery high (10^-4 to 10^-6 TF); LoD scales with #loci x inputLower for MRD; few loci per region
Needs tumor tissueYes (design step, weeks of turnaround)No (tissue-free, faster)
CHIP confoundingLow (tracks known tumor somatic variants)High (de novo calls include clonal hematopoiesis)
Best useDefined-burden MRD/surveillance after curative intentNo tissue available, or broad genotyping in metastatic disease
ScenarioRecommendedWhy
Post-curative-intent MRD / recurrence surveillanceTumor-informed bespoke, binary callReaches ppm LoD by integrating across the personal variant set; CHIP-resistant
No tissue available, metastatic response monitoringTumor-naive panel, track aggregated burdenTissue-free and immediate; accept higher LoD and mandatory CHIP control
Post-surgical landmark (single decisive timepoint)One draw at ~2-10 weeks post-opAvoids the surgical cfDNA surge; conventional Week 4 default
Serial surveillance over months-yearsTrend over >=2 consecutive draws, confirm before actingEach draw is another false-positive opportunity (multiple testing)
Defining "molecular response"Use the assay's own validated cutoff; do not import "2-log" or "90%" blindlyCutoffs are non-harmonized across assays (see below)

Methodology evolves: verify the current best practice and the assay's validated definitions against the latest tool/vendor documentation before fixing any threshold in code.

ctDNA Kinetics Biology -- why timing and shedding gate interpretation

ctDNA has a plasma half-life of roughly 2 h (114 min, Diehl 2008); broader literature spans ~16 min to 2.5 h. This fast turnover is the entire reason serial monitoring works: plasma concentration tracks CURRENT tumor flux, not a weeks-old average, while imaging tumor volume lags. The same fast clearance makes landmark timing fragile. Surgery dumps a transient cfDNA surge into plasma (tissue trauma, wound healing, neutrophil extracellular traps) that dilutes tumor fraction and can transiently raise total cfDNA. Drawing at post-op day 1-3 reads this surge, not residual disease; the conventional landmark window is ~2-10 weeks (Week 4 a frequent default). A clearance fit that includes a post-op surge point mis-estimates the half-life.

Shedding is not uniform. "ctDNA-negative" does NOT equal "disease-free": some early lung adenocarcinomas and indolent/low-volume tumors shed below detectable thresholds, and brain metastases behind the blood-brain barrier shed poorly into plasma (CSF is the better CNS compartment). A patient can have radiographic progression with clean plasma. Negativity has high negative predictive value for relapse in shedding tumors but is never a guarantee -- imaging stays mandatory for low/non-shedders and sanctuary sites.

Molecular-Response Definitions -- and the non-standardization caveat

TermRepresentative operationalizationCaveat
Molecular response (MR)>= 90% drop (ctMoniTR-style) or >= 2-log/100x (immuno/heme heritage) from baseline2-log and 90% are different magnitudes; cutoff is study/assay-specific
Molecular complete response (mCR)ctDNA becomes undetectable"Undetectable" is LoD-conditional, not zero
ctDNA clearanceSustained detectable -> undetectableDepends on input/depth of the clearing draw; confirm with re-draw
Molecular progression / relapseConfirmed re-detection or rise-from-nadirRequire trend over >=2 draws (multiple testing)

These definitions are NOT harmonized. "2-log reduction," "90% reduction," and "molecular complete response" are assay- and study-dependent, not interchangeable. The Friends of Cancer Research ctMoniTR project is the field's standardization attempt (pooling ctDNA-change data across NSCLC immunotherapy studies to validate ctDNA change as an intermediate endpoint), not a settled standard. The FDA ctDNA guidance for curative-intent solid-tumor drug development was issued as a draft in May 2022 and finalized in November 2024; it endorses ctDNA for patient selection, MRD-based enrichment, and as a measure of response, but does NOT yet endorse ctDNA change as a validated surrogate endpoint for DFS/EFS/OS. Code should accept the assay's own validated cutoff rather than baking one in.

Clinical Evidence and Lead Time

ctDNA MRD predicts relapse months before imaging across tumor types: breast median ~8 mo (Garcia-Murillas 2015), NSCLC median ~5.2 mo (Chaudhuri 2017), CRC mean ~8.7 mo (Reinert 2019); TRACERx phylogenetic ctDNA tracks clonal evolution and metastatic seeding (Abbosh 2017, 2023). The interventional landmark is DYNAMIC (Tie 2022): a ctDNA-guided strategy in stage II colon cancer reduced adjuvant chemotherapy use (15% vs 28%) without compromising 2-year recurrence-free survival, proving an MRD-negative call can justify de-escalation. Caveat -- lead-time bias: "ctDNA detects relapse N months before imaging" is a real analytic-sensitivity advantage, but measuring survival from molecular detection vs clinical detection merely moves the clock back and inflates apparent survival. Demonstrating clinical utility (that acting on the earlier signal improves outcomes) requires an interventional design like DYNAMIC, not earlier detection alone. Flag lead-time bias wherever lead time is reported.

Tumor-Fraction Trend with Baseline and Nadir

Goal: Summarize a serial trajectory into baseline, nadir, and baseline-referenced change, with below-LoD points marked as censored, not zero.

Approach: Sort by time, carry a per-sample LoD column, flag any point at-or-below its LoD as left-censored, and compute log-fold change from baseline only on the uncensored estimates (substituting the LoD bound, never 0, for censored points).

python
import numpy as np
import pandas as pd

def summarize_trajectory(df):
    '''df columns: timepoint, tumor_fraction, per_sample_lod (genome-equivalent-aware).'''
    df = df.sort_values('timepoint').copy()
    df['censored'] = df['tumor_fraction'] <= df['per_sample_lod']
    df['tf_for_log'] = np.where(df['censored'], df['per_sample_lod'], df['tumor_fraction'])
    baseline = df.iloc[0]['tf_for_log']
    df['log2_fc_baseline'] = np.log2(df['tf_for_log'] / baseline)
    detected = df[~df['censored']]
    nadir = detected['tumor_fraction'].min() if len(detected) else np.nan
    return df, {'baseline_tf': baseline, 'nadir_tf': nadir, 'n_censored': int(df['censored'].sum())}

Mutation Tracking and Censoring-Aware Clearance Kinetics

Goal: Pivot per-mutation VAF over time and estimate a clearance half-life only over the genuine decay phase, treating below-LoD timepoints as censored.

Approach: Build a timepoint-by-mutation pivot, mark cleared loci as below-LoD (not missing-equals-zero), then fit ln(VAF) ~ time by OLS over the monotonic-decay phase only, excluding the surgical-surge point, any post-nadir rebound, and all censored points; half-life = ln(2)/(-slope).

python
from scipy import stats

def clearance_half_life(df, lod):
    '''df columns: timepoint, vaf for one mutation. lod = per-sample detection bound.
       Fits the uncensored decay phase up to the nadir (drops post-nadir rebound and
       every below-LoD point); never feeds log(0) into the OLS.'''
    df = df.sort_values('timepoint')
    uncensored = df[df['vaf'] > lod].reset_index(drop=True)
    if len(uncensored) < 3:
        return None
    decay = uncensored.iloc[:uncensored['vaf'].idxmin() + 1]
    if len(decay) < 3:
        return None
    fit = stats.linregress(decay['timepoint'].values, np.log(decay['vaf'].values))
    half_life = np.log(2) / -fit.slope if fit.slope < 0 else np.inf
    return {'half_life_days': half_life, 'slope': fit.slope, 'r_squared': fit.rvalue ** 2,
            'n_points': len(decay), 'n_censored_excluded': int((df['vaf'] <= lod).sum())}

Molecular-Relapse Calling

Goal: Call molecular relapse from confirmed re-detection or sustained rise-from-nadir, not a single excursion.

Approach: Find the nadir, then require detection (above per-sample LoD) on >=2 consecutive post-nadir draws, or a rise above an assay-defined margin above nadir confirmed on a re-draw; annotate every call with the draw's per-sample LoD so a low-LoD draw is not mistaken for new biology.

python
def call_molecular_relapse(df, rise_factor=2.0, min_consecutive=2):
    '''df columns: timepoint, tumor_fraction, per_sample_lod. Requires a confirmed trend.'''
    df = df.sort_values('timepoint').copy()
    df['detected'] = df['tumor_fraction'] > df['per_sample_lod']
    nadir_time = df.loc[df['tumor_fraction'].idxmin(), 'timepoint']
    nadir_tf = max(df['tumor_fraction'].min(), df['per_sample_lod'].min())  # floor at LoD, not a censored value
    post = df[df['timepoint'] > nadir_time]
    consec = (post['detected'] & (post['tumor_fraction'] > nadir_tf * rise_factor)).astype(int)
    run = consec.groupby((consec == 0).cumsum()).cumsum().max() if len(consec) else 0
    relapse = bool(run >= min_consecutive)
    return {'relapse': relapse, 'nadir_tf': nadir_tf, 'confirmed_consecutive': int(run)}
Show full SKILL.md (901 more words)Show less

Per-Method Failure Modes

Naive per-timepoint VAF thresholding

Trigger: applying "VAF < X" per timepoint to a multi-locus assay. Mechanism: discards the integration that makes MRD work; one noisy locus calls positive. Symptom: inflated false positives, jumpy trajectory. Fix: use the assay's integrated binary detected/not-detected call across the full variant set.

Treating undetectable as a true zero

Trigger: plugging 0.0 (or VAF/2) into a log-fit or fold-change. Mechanism: log(0) is undefined; substituting a small number biases slope and fold-change. Symptom: NaN/inf fits or implausibly fast clearance. Fix: treat below-LoD as left-censored at the per-sample LoD; report "below LoD = X," never "0%."

Ignoring per-timepoint LoD changes with input mass

Trigger: comparing "undetectable" across draws of different cfDNA input. Mechanism: LoD is input-conditional; a low-input draw could not have seen the prior burden. Symptom: spurious "clearance" or "relapse" at draws with anomalous input. Fix: carry per-sample LoD/genome-equivalents as a covariate; down-weight low-input negatives.

CHIP rising over time read as relapse

Trigger: tumor-naive longitudinal panel without matched WBC sequencing. Mechanism: clonal hematopoiesis clones expand over time and under chemotherapy (Razavi 2019: majority of plasma variants are CHIP-derived), producing a rising non-tumor "ctDNA" signal. Symptom: false molecular progression in DNMT3A/TET2/ASXL1 hotspots. Fix: tumor-informed tracking, or matched serial WBC sequencing / known-CHIP-gene blacklisting.

Lead-time bias in outcome claims

Trigger: reporting survival from molecular detection vs clinical detection. Mechanism: moving the detection clock back inflates apparent survival without changing outcome. Symptom: a "benefit" that is an artifact of earlier detection. Fix: claim clinical utility only from interventional designs (DYNAMIC); label lead time as analytic sensitivity, not benefit.

Quantitative Thresholds

ThresholdSourceRationale
ctDNA plasma half-life ~114 min (~2 h)Diehl 2008, Nat Med 14:985Single-patient post-op estimate; broader range 16 min-2.5 h. Sets why monitoring works and why post-op timing matters
Post-op landmark window ~2-10 weeks (Week 4 common)Convention across DYNAMIC/Signatera/RaDaRLate enough for the surgical cfDNA surge to clear before reading residual disease
~15,000 haploid genome-equivalents per 10 mL tube (~50 ng cfDNA, ~300 GE/ng)Standard biophysical constantsHard sampling floor: at 0.01% TF that is ~1.5 expected tumor molecules
Poisson-limited regime: lambda < 3 expected tumor moleculesPoisson detection theory (1-e^-3=0.95)Below this, detection is stochastic; small input/recovery shifts flip a result across the LoD
Bespoke MRD sensitivity 10^-4 to 10^-6 tumor fractionINVAR (Wan 2020), Signatera (Reinert 2019), RaDaRAchieved only by integrating across the personal variant set, not per-locus
Molecular response ~2-log (100x) or ~90% reductionctMoniTR (Vega 2022); immuno/heme heritageNon-harmonized convention -- surface the assay's own validated cutoff, do not hard-code
Per-course false-positive risk = 1 - s^n (s = per-sample specificity, n = draws)Multiple-testing arithmetics=0.995,n=12 -> ~5.8%; s=0.99,n=12 -> ~11%. Report specificity per monitoring course, confirm positives by re-draw

Common Errors

Error / symptomCauseSolution
log(0) / inf in clearance fitCensored (below-LoD) point fed into ln(VAF)Fit only the uncensored decay phase; carry LoD as the censoring bound
Half-life implausibly short or fits the surgePost-op surge or post-nadir rebound point includedRestrict the OLS to the monotonic on-treatment decay phase
"Relapse" at one noisy drawActing on a single positiveRequire >=2 consecutive confirmed draws; re-draw before acting
Rising signal in a tissue-free panel mistaken for tumorCHIP drift over timeMatched WBC sequencing or tumor-informed tracking
"Negative = cured" overcallLow-shedder / sanctuary site / low-input drawFrame negative as below-LoD; keep imaging for low/non-shedders

References

  • Diehl F, et al. 2008. Circulating mutant DNA to assess tumor dynamics. Nature Medicine 14:985-990. -- ctDNA half-life ~114 min; post-resection clearance kinetics.
  • Tie J, et al. 2022. Circulating Tumor DNA Analysis Guiding Adjuvant Therapy in Stage II Colon Cancer (DYNAMIC). New England Journal of Medicine 386:2261-2272. -- Interventional MRD-guided de-escalation.
  • Abbosh C, et al. 2017. Phylogenetic ctDNA analysis depicts early-stage lung cancer evolution. Nature 545:446-451. -- TRACERx tumor-informed clonal tracking.
  • Abbosh C, et al. 2023. Tracking early lung cancer metastatic dissemination in TRACERx using ctDNA. Nature 616:553-562. -- Deep tumor-informed surveillance (~200 mutations).
  • Garcia-Murillas I, et al. 2015. Mutation tracking in circulating tumor DNA predicts relapse in early breast cancer. Science Translational Medicine 7:302ra133. -- Lead time ~8 mo in breast cancer.
  • Wan JCM, et al. 2020. ctDNA monitoring using patient-specific sequencing and integration of variant reads (INVAR). Science Translational Medicine 12:eaaz8084. -- Per-sample LoD derived from informative reads; the formal binary-integration framing.
  • Reinert T, et al. 2019. Analysis of Plasma Cell-Free DNA by Ultradeep Sequencing in Patients With Stages I to III Colorectal Cancer. JAMA Oncology 5:1124-1131. -- Signatera; serial HR ~43.5; mean lead ~8.7 mo.
  • Chaudhuri AA, et al. 2017. Early Detection of Molecular Residual Disease in Localized Lung Cancer by Circulating Tumor DNA Profiling. Cancer Discovery 7:1394-1403. -- CAPP-Seq; median lead ~5.2 mo.
  • Razavi P, et al. 2019. High-intensity sequencing reveals the sources of plasma circulating cell-free DNA variants. Nature Medicine 25:1928-1937. -- Majority of plasma cfDNA variants are CHIP-derived; matched WBC sequencing essential.
  • Merino Vega D, et al. 2022. Changes in Circulating Tumor DNA Reflect Clinical Benefit Across Multiple Studies of Patients With Non-Small-Cell Lung Cancer Treated With Immune Checkpoint Inhibitors. JCO Precision Oncology 6:e2100372. -- Friends of Cancer Research ctMoniTR Step 1; the molecular-response standardization effort, not a settled threshold.

The RaDaR/LUCID early-NSCLC residual-ctDNA study (Annals of Oncology 2022, 33:500-510) is referenced generically above; verify first-author attribution and the exact article identifier against the journal record before citing it formally.

  • ctdna-mutation-detection - detect the variant set that is then tracked
  • tumor-fraction-estimation - per-timepoint tumor burden
  • analytical-validation - per-timepoint LoD and left-censoring of undetectable samples
  • fragment-analysis - fragmentomic trends as a complementary monitoring signal
  • clinical-biostatistics/survival-analysis - relapse, lead-time, and endpoint analysis

© GPTomics, 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 2 other files in liquid-biopsy/longitudinal-monitoring of GPTomics/bioSkills.

  • SKILL.md
  • examples/longitudinal_monitoring.py
  • usage-guide.md

Open the folder on GitHubat commit d91ed3d

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in GPTomics/bioSkills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Bio Longitudinal Monitoring 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.

Bio Longitudinal Monitoring compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bio Longitudinal Monitoring this skillGPTomics/bioSkills1.2k1 repos~5.1kAutomated safety check: PassMIT
MatplotlibzLanqing/codex-claude-academic-skills4.7k17 repos~2.9kAutomated safety check: PassMIT
Exploratory Data Analysisspacering-net/codeg3.9k14 repos~3.6kAutomated safety check: PassMIT
Scikit LearnzLanqing/codex-claude-academic-skills4.7k16 repos~3.9kAutomated safety check: PassBSD-3-Clause
Chart Visualizationbytedance/deer-flow84k1 repos~840Automated safety check: PassMIT
TimesFM Forecastinggoogle-research/timesfm34k—~4.7kAutomated safety check: PassApache-2.0

Similar skills

  • Matplotlib

    zLanqing/codex-claude-academic-skills

    Low-level plotting library for full customization. An agent skill from zLanqing/codex-claude-academic-skills.

    4.7k GitHub starsUsed in 17 repos~2.9k tokens
    Data & AnalyticsAuto-check passed
  • Exploratory Data Analysis

    spacering-net/codeg

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

    3.9k GitHub starsUsed in 14 repos~3.6k tokens
    Data & AnalyticsAuto-check passed
  • Scikit Learn

    zLanqing/codex-claude-academic-skills

    Machine learning in Python with scikit-learn. An agent skill from zLanqing/codex-claude-academic-skills.

    4.7k GitHub starsUsed in 16 repos~3.9k tokens
    Data & AnalyticsAuto-check passed
  • Chart Visualization

    bytedance/deer-flow

    Picks a suitable chart type from 26 options for your data, maps the data to that chart's parameters and generates a chart image through a JavaScript script.

    84k GitHub starsUsed in 1 repo~840 tokens
    Data & AnalyticsAuto-check passed
  • TimesFM Forecasting

    google-research/timesfm

    Forecasts any univariate time series zero-shot with Google's TimesFM model, returning point forecasts and calibrated prediction intervals without training.

    34k GitHub stars~4.7k tokensUpdated 11 days ago
    Data & AnalyticsAuto-check passed
  • Sandbox Bench

    vercel/next.js

    Official

    Benchmark React or Next.js changes on Vercel Sandbox VMs with paired A/B statistics: react PR/commit vs base, or Next.js PR/commit vs base, measured end-to-end through the bench/render-pipeline app…

    143k GitHub stars~4.1k tokensUpdated today
    Data & AnalyticsAuto-check passed

More from GPTomics/bioSkills

All 559 skills in this repo
  • Bio Alignment Io

    GPTomics/bioSkills

    Read, write, and convert multiple sequence alignment files using Biopython Bio.AlignIO.

    1.2k GitHub starsUsed in 3 repos~4.9k tokens
    Auto-check passed
  • bioSkills Installer

    GPTomics/bioSkills

    Installs the bioSkills collection of 425 bioinformatics skills in one step, or only chosen categories, so sequencing, RNA-seq, single-cell and variant tasks get specialized help.

    1.2k GitHub starsUsed in 1 repo~789 tokens
    Auto-check passed
  • Bio Write Sequences

    GPTomics/bioSkills

    Write biological sequences to files (FASTA, FASTQ, GenBank, EMBL) using Biopython Bio.SeqIO.

    1.2k GitHub starsUsed in 3 repos~2.1k tokens
    Auto-check passed
  • Amplicon Primer Clipping

    GPTomics/bioSkills

    Soft- or hard-clips PCR primer footprints from aligned amplicon BAMs so primer bases stop masquerading as confirmed reference sequence.

    1.2k GitHub starsUsed in 2 repos~2.2k tokens
    Auto-check passed
  • Filters BAM alignments by FLAG bits, mapping quality and regions with samtools view or pysam, with recipes for common keep and drop cases.

    1.2k GitHub starsUsed in 2 repos~3.6k tokens
    Auto-check passed
  • Bio Alignment Indexing

    GPTomics/bioSkills

    Create and use BAI/CSI indices for BAM/CRAM files using samtools and pysam.

    1.2k GitHub starsUsed in 2 repos~2.4k tokens
    Auto-check passed

Questions about Bio Longitudinal Monitoring

What does Bio Longitudinal Monitoring do?

Tracks ctDNA across serial liquid-biopsy timepoints for molecular residual disease (MRD) and treatment-response monitoring, treating MRD as a binary integrated detection call across the patient's…. Bio Longitudinal Monitoring is an agent skill from GPTomics/bioSkills. Tracks ctDNA across serial liquid-biopsy timepoints for molecular residual disease (MRD) and treatment-response monitoring, treating MRD as a binary integrated detection call across the patient's full variant set (with a defined LoD95 and per-sample specificity) rather than a per-timepoint VAF threshold, and handling undetectable samples as left-censored at the per-sample limit of detection rather than true zeros.

When should I use Bio Longitudinal Monitoring?

Bio Longitudinal Monitoring fits situations like: monitoring ctDNA during therapy; calling molecular relapse before imaging; estimating clearance half-life from serial samples.

How do I install Bio Longitudinal Monitoring in Claude Code?

Run `npx skills add GPTomics/bioSkills --skill bio-longitudinal-monitoring -a claude-code`. Or copy the skill folder (liquid-biopsy/longitudinal-monitoring in GPTomics/bioSkills) into .claude/skills/bio-longitudinal-monitoring in your project. Claude Code loads it when a task matches its description.

How do I install Bio Longitudinal Monitoring in Codex?

Run `npx skills add GPTomics/bioSkills --skill bio-longitudinal-monitoring -a codex`. Or copy the skill folder (liquid-biopsy/longitudinal-monitoring in GPTomics/bioSkills) into .agents/skills/bio-longitudinal-monitoring in your project. Codex loads it when a task matches its description.

Can I use Bio Longitudinal Monitoring 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 GPTomics/bioSkills --skill bio-longitudinal-monitoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bio-longitudinal-monitoring, .gemini/skills/bio-longitudinal-monitoring, .github/skills/bio-longitudinal-monitoring and .opencode/skills/bio-longitudinal-monitoring in your project.

What does Bio Longitudinal Monitoring need to run?

Going by SKILL.md and its folder, Bio Longitudinal Monitoring needs Python for the scripts in its folder and the command-line tools its instructions call (pip). Our summary lists: Python 3.

Does Bio Longitudinal Monitoring access the network?

SKILL.md contains no URLs. Its commands use pip, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Bio Longitudinal Monitoring 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 Bio Longitudinal Monitoring use?

Bio Longitudinal Monitoring is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Bio Longitudinal Monitoring use?

About 5.1k tokens (SKILL.md is roughly 21k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Bio Longitudinal Monitoring?

Skills that share tags, products or a category with Bio Longitudinal Monitoring: Matplotlib (zLanqing/codex-claude-academic-skills, 4.7k stars), Exploratory Data Analysis (spacering-net/codeg, 3.9k stars), Scikit Learn (zLanqing/codex-claude-academic-skills, 4.7k stars) and Chart Visualization (bytedance/deer-flow, 84k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bio Longitudinal Monitoring?

GPTomics (a GitHub organization) maintains it in GPTomics/bioSkills, which has 1,218 GitHub stars. The repository holds 559 skills in this directory. The repository was last updated on August 15, 2026.

Source: GPTomics/bioSkills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.