Agent skill

Bio Analytical Validation

by GPTomics in GPTomics/bioSkills

Treats a ctDNA assay as a molecule-counting experiment at the Poisson edge and builds its analytical-validation case the measurement-science way.

MITAuto-check passedResearch & Science

Install Bio Analytical Validation

skills CLI
$ npx skills add GPTomics/bioSkills --skill bio-analytical-validation -a claude-code

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

GitHub CLI
$ gh skill install GPTomics/bioSkills bio-analytical-validation --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/analytical-validation .claude/skills/bio-analytical-validation && 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-analytical-validation
GitHub stars
1.2k
Used in
1 other repo
Token cost
~4.2k tokens
SKILL.md length
1,816 words
Files
3
Skills in repo
552
Repo updated
First seen
Licence
MIT

At a glance

Treats a ctDNA assay as a molecule-counting experiment at the Poisson edge and builds its analytical-validation case the measurement-science way.

  • Trusting a sensitivity claim
  • SKILL.md covers Version Compatibility, The Single Most Important…, Methods Landscape and Decision Tree by Scenario, plus 7 more sections
  • Runs Python scripts from its folder; calls pip
  • Designing a dilution-series validation

What it does

Bio Analytical Validation is an agent skill from GPTomics/bioSkills. Treats a ctDNA assay as a molecule-counting experiment at the Poisson edge and builds its analytical-validation case the measurement-science way. Covers the genome-equivalent currency (~330 haploid copies/ng), the lambda = inputGE x VAF sampling ceiling (lambda=3 for ~95% detection), the error-suppression ladder (raw NGS ~1e-3 - single-strand UMI ~1e-4/1e-5 - duplex <1e-7), the CLSI EP17 LoB/LoD/LoD95/LoQ framework, the per-locus-vs-panel-integrated LoD distinction that lets bespoke MRD reach ppm, contrived/SEQC2…

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

It sits in Research & Science, covering Bioinformatics. 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

  • Trusting a sensitivity claim
  • Designing a dilution-series validation
  • Deciding how many genome equivalents are needed at a target VAF
  • Choosing a single-locus vs panel-integrated LoD

Example prompts

  • “detects 0.1% VAF”
  • “Use the bio-analytical-validation skill to treat a ctDNA assay as a molecule-counting experiment at the Poisson edge and builds its…”
  • “/bio-analytical-validation”

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 Analytical Validation loads about 4.2k tokens when it runs. Until then it costs about 228 tokens; SKILL.md has 1,816 words of instructions outside code blocks.

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

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). 1,816 words, ~4,177 tokens.

Download SKILL.mdSave it as .claude/skills/bio-analytical-validation/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
bio-analytical-validation
description
Treats a ctDNA assay as a molecule-counting experiment at the Poisson edge and builds its analytical-validation case the measurement-science way. Covers the genome-equivalent currency (~330 haploid copies/ng), the lambda = input_GE x VAF sampling ceiling (lambda>=3 for ~95% detection), the error-suppression ladder (raw NGS ~1e-3 -> single-strand UMI ~1e-4/1e-5 -> duplex <1e-7), the CLSI EP17 LoB/LoD/LoD95/LoQ framework, the per-locus-vs-panel-integrated LoD distinction that lets bespoke MRD reach ppm, contrived/SEQC2 reference standards, and honest LoD reporting conditioned on input mass + consensus depth + replicate detection rate. Use when stating or trusting a sensitivity claim, designing a dilution-series validation, deciding how many genome equivalents are needed at a target VAF, choosing a single-locus vs panel-integrated LoD, or auditing a "detects 0.1% VAF" claim.
tool_type
python
primary_tool
scipy

Version Compatibility

Reference examples tested with: numpy 1.26+, scipy 1.12+, statsmodels 0.14+

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.

Analytical Validation and Detection Limits

"What is the real limit of detection of my ctDNA assay, and can I trust the number I am about to report?" -> Quantify the Poisson sampling ceiling, the error-suppression floor, and the LoB/LoD/LoQ that together define a defensible sensitivity claim.

  • Python: scipy.stats.poisson for detection-probability math, scipy.stats.norm for CLSI LoB/LoD, statsmodels Probit/Logit for a dilution-series LoD95 fit.

The Single Most Important Modern Insight -- LoD Is Set by Genome Equivalents Sampled and Error Suppression, NOT by Sequencing Depth or the Caller

A ctDNA assay is a molecule-counting experiment at the Poisson edge. The mutant signal is a fixed, tiny number of physical template molecules in the tube, and the limit of detection is governed by two ceilings: how many genome equivalents were sampled (Poisson), and how low the background error floor was driven (error suppression). 1 ng of human DNA is ~330 haploid genome equivalents; the expected mutant-molecule count is lambda = input_GE x VAF. A 0.1% variant on 1,000 GE (~3.0 ng) has lambda = 1, so e^-1 ~= 37% of the time the mutant template was never in the tube and a perfect sequencer detects nothing. Past the point where every input molecule has been read once (sampling saturation, visible as a deduplication plateau in UMI families), additional read depth re-sequences the same physical molecules and adds zero information. Reporting an LoD as a bare VAF -- with no input mass, no unique-molecule (consensus) depth, no replicate detection rate -- is reporting an undefined quantity.

The second ceiling is the per-base background error rate, which sets the VAF floor independently: a 0.1% variant cannot be distinguished from noise if the assay manufactures that base at 0.1%. Error suppression is a ladder (raw NGS ~1e-3 -> single-strand UMI consensus ~1e-4/1e-5 -> duplex <1e-7), and single-strand consensus does NOT remove template-resident damage (C->T deamination, G->T 8-oxoG) because every PCR copy of that strand inherits the lesion -- only duplex strand-concordance catches it. The achieved LoD is the worse of the two ceilings: error dominates above ~0.1% VAF for tumor-naive single-locus calling, sampling dominates below it. The escape hatch is integration -- a bespoke panel summing mutant molecules across 16-50 loci against summed background reaches single-ppm even though each locus alone is ~1e-3 to 1e-4 (per-locus vs panel-integrated LoD).

Methods Landscape

ConceptDefinitionSource
LoB (Limit of Blank)Highest signal expected from an analyte-free blank (95th pct): LoB = mean_blank + 1.645*SD_blank; the false-positive anchor on true negativesCLSI EP17-A2
LoD (Limit of Detection)Lowest level reliably distinguishable from LoB: LoD = LoB + 1.645*SD_low; a sample at LoD is detected ~95% of the timeCLSI EP17-A2
LoD95The concentration/VAF where detection probability = 95%; a point on a probit/logistic detection curve, not a separate definitionCLSI EP17-A2; Newman 2016
LoQ (Limit of Quantitation)Lowest level measurable with stated precision (e.g. CV<=20%); LoQ >= LoD always, so a "VAF" near the floor is detectable but not trustworthyCLSI EP17-A2
Per-locus LoDSingle-variant LoD; sampling- and error-limited (~0.05-0.1% VAF typical)Newman 2014/2016
Panel-integrated LoDEvidence summed across N tracked variants via a >=k-of-N positivity rule (binomial over per-locus Poisson detection), reaching single-ppm at 16-50 loci; ~sqrt(N) variance-averaging is only a loose lower boundReinert 2019
Reference standardsContrived defined-VAF cell-line admixtures fragmented to ~160 bp into normal cfDNA; SEQC2 Sample A / HCC1395 truth setsFang 2021 (SEQC2)

Decision Tree by Scenario

ScenarioRecommendedWhy
"How many GE for 95% detection at VAF X?"Solve lambda = input_GE x VAF >= 3, so input_GE >= 3/VAF1 - e^-3 = 0.95; ~30,000 GE (~91 ng at 330 GE/ng) for a single 1e-4 variant -- often more than one tube provides
"Why is more depth not helping?"Report unique (consensus) molecular coverage, not raw depth; check the dedup plateauPast sampling saturation, depth re-reads the same molecules; the ceiling is GE in the tube
Single hotspot vs bespoke panel for low VAFSingle locus: error/sampling-limited ~0.1%; need ppm -> integrate across 16-50 clonal lociPer-locus Poisson/error floor is escaped only by summing independent detections (panel-integrated LoD)
Reporting an LoDCondition on input mass (GE) + consensus depth + replicate detection rate (e.g. "LoD95 0.1% VAF at 30 ng / 2x duplex / 95% of 20 replicates")A bare VAF omits the input mass, the unique depth, and per-locus vs integrated -- it is undefined
Estimating LoD95 from a dilution seriesProbit (or logistic) regression of detection (0/1) on VAF; read off the 95% point with a CICLSI EP17-A2 detection-curve method; binary detection is a clean GLM target
Distinguishing detection from quantitationSet LoD for yes/no calls; set LoQ (CV<=20%) separately for any reported VAF/TFMRD calls are binary and can sit far below LoQ; a near-floor VAF number is not quantitative
Validating against truthContrived SEQC2 Sample A / HCC1395 admixtures, fragmented to cfDNA-like ~160 bpReal low-VAF patient material is scarce/unverifiable; commutability with plasma is the caveat

Genome-Equivalent and Poisson Detection Calculator

Goal: Convert an input mass and target VAF into an expected mutant-molecule count and a detection probability, so a sensitivity claim is anchored to molecules rather than to a VAF alone.

Approach: Convert ng to haploid genome equivalents (~330/ng), set lambda = input_GE x VAF, and read the detection probability as a Poisson tail P(X >= k) = 1 - cdf(k-1, lambda); invert for the minimum GE that puts lambda at the >=3 sampling-detection threshold.

python
import numpy as np
from scipy.stats import poisson

GE_PER_NG = 330  # haploid ~3.3 pg -> strict 1 ng / 3.3 pg = 303; 330 is the common diploid-6.6 pg/rounding convention

def genome_equivalents(input_ng):
    return input_ng * GE_PER_NG

def detection_probability(input_ng, vaf, min_mutant_molecules=1):
    '''P(at least min_mutant_molecules present) under Poisson(lambda = GE * VAF).'''
    lam = genome_equivalents(input_ng) * vaf
    return float(poisson.sf(min_mutant_molecules - 1, lam))

def ge_for_sampling_detection(vaf, target_lambda=3.0):
    '''GE needed so lambda >= 3 -> ~95% chance the mutant molecule is present at all.'''
    return target_lambda / vaf

# A 0.1% variant on 3.0 ng (~990 GE) has lambda ~= 1 -> ~63% detected, ~37% missed by sampling alone.
detection_probability(3.0, 0.001)          # ~0.63
ge_for_sampling_detection(1e-4)            # 30000 GE (~91 ng) for a single 0.01% variant

LoB and LoD95 from a Dilution Series (CLSI EP17 style)

Goal: Estimate the VAF at which the assay detects 95% of the time, from a contrived dilution series, and anchor it to the blank-derived false-positive floor.

Approach: Compute LoB from blank replicates (mean + 1.645*SD, one-sided 95th pct), then fit a probit GLM of binary detection on log10(VAF) (CLSI EP17 fits on log concentration) across the dilution series and invert it for the 95% detection point. The series must bracket the 0.95 crossing — all-detected upper levels cause near-complete separation and an unstable slope.

python
import numpy as np
import statsmodels.api as sm
from scipy.stats import norm

def limit_of_blank(blank_signals):
    '''LoB = mean + 1.645*SD; one-sided 95th percentile of analyte-free blanks.'''
    blank_signals = np.asarray(blank_signals, dtype=float)
    return blank_signals.mean() + 1.645 * blank_signals.std(ddof=1)

def lod95_probit(vaf_levels, detected):
    '''Probit fit of detection (0/1) on log10(VAF); returns the VAF where P(detect) = 0.95.'''
    log_vaf = np.log10(np.asarray(vaf_levels, dtype=float))
    y = np.asarray(detected, dtype=float)
    X = sm.add_constant(log_vaf)
    fit = sm.GLM(y, X, family=sm.families.Binomial(link=sm.families.links.Probit())).fit()
    intercept, slope = fit.params
    return 10 ** ((norm.ppf(0.95) - intercept) / slope)

Per-Locus to Panel-Integrated LoD

Goal: Combine independent per-locus detection probabilities into the panel-level detection probability that a bespoke MRD assay actually achieves, and find the integrated LoD.

Approach: Treat each tracked locus as an independent Poisson sampler at the same tumor VAF; a panel positive call requires at least k loci detected, so the panel detection probability is the binomial-tail over the per-locus probabilities -- this is why summing 16-50 loci reaches ppm.

python
import numpy as np
from scipy.stats import poisson, binom

def panel_detection_probability(input_ng, vaf, n_loci, min_loci_positive=2):
    '''P(>= min_loci_positive of n_loci detected); >=2-of-N is the Signatera-style positivity rule.'''
    per_locus = float(poisson.sf(0, input_ng * 330 * vaf))
    return float(binom.sf(min_loci_positive - 1, n_loci, per_locus))

def panel_integrated_lod95(input_ng, n_loci, min_loci_positive=2, grid=None):
    '''Lowest VAF on a log grid where the >=k-of-N panel call hits 95%.'''
    grid = np.logspace(-6, -2, 400) if grid is None else np.asarray(grid)
    probs = [panel_detection_probability(input_ng, v, n_loci, min_loci_positive) for v in grid]
    hits = grid[np.asarray(probs) >= 0.95]
    return float(hits.min()) if hits.size else float('nan')
Show full SKILL.md (731 more words)Show less

Quantitative Thresholds

ThresholdSourceRationale
~330 haploid genome equivalents per ng cfDNAStandard (haploid ~3.3 pg)Converts input mass to the molecule count that actually sets sensitivity; strict 1 ng / 3.3 pg = 303, with 330 the common diploid-6.6 pg/rounding convention
lambda = input_GE x VAF; lambda >= 3 for ~95% sampling-detectionPoisson, 1 - e^-3 = 0.95Below lambda~3 the mutant template is often simply absent from the tube regardless of sequencing
Raw NGS error floor ~1e-3Schmitt 2012 context; field consensusSets the per-base VAF floor before any consensus; a global VAF cutoff above this is noise-limited
Single-strand UMI consensus ~1e-4 to 1e-5Newman 2014/2016 (CAPP-Seq/iDES)Majority-vote within a UMI family erases PCR/sequencing error not shared across the family
Duplex sequencing <1e-7 (theory <1/1e9 nt)Schmitt 2012 PNAS 109:14508Requires the variant on BOTH original strands; independent strand errors cannot agree
iDES adds ~3-15x over baseline; ctDNA to ~4e-5Newman 2016 Nat Biotechnol 34:547Position/trinucleotide background model subtracts stereotyped artifacts per locus
ichorCNA tumor-fraction floor ~3%Adalsteinsson 2017 Nat Commun 8:1324Copy-number-based TF estimation; sWGS/ULP-WGS cannot resolve TF below ~3% -- an LoD, not a VAF
Bespoke panel reaches single-ppm by integrating 16-50 lociReinert 2019 JAMA Oncol 5:1124Per-locus ~1e-4 floor escaped by summing independent detections; >=2-of-N positivity rule
LoQ >= LoD (e.g. CV<=20% for quantitation)CLSI EP17-A2Detection (binary) is easier than quantitation (continuous); near-floor VAFs are not trustworthy numbers

Common Errors

Error / symptomCauseSolution
"Assay detects 0.1% VAF" with no input massVAF reported as a standalone sensitivity specCondition the LoD on input GE + consensus depth + replicate detection rate; 0.1% on 100 GE is noise
Buying more sequencing depth to improve sensitivityConflating read depth with molecule countPast the dedup plateau the assay is sampling-saturated; add plasma volume / conversion efficiency, not depth
Per-locus LoD quoted as the panel LoD (or vice versa)Ignoring integration across tracked lociState which is reported; a 50-variant panel's integrated LoD is orders of magnitude below any single locus
VAF used as the sensitivity unitOmitting the molecule count behind the fractionPair every VAF with input GE; lambda = GE x VAF is the quantity that determines detection
Single-strand UMI assumed to remove damage artifactsTemplate-resident C->T/G->T inherited by every copyUse duplex strand-concordance for sub-1e-5 claims; single-strand votes unanimously for the lesion
Reporting a near-floor VAF as a measured valueConfusing LoD (detect) with LoQ (quantify)Quantitative VAF/TF only at/above LoQ (CV<=20%); below it report detected/not-detected
Global VAF cutoff across all lociBackground error is position/context-dependentUse a per-locus background model (iDES-style); a flat threshold loses sensitivity and specificity

References

  • Diehl F, Schmidt K, Choti MA, et al. 2008. Circulating mutant DNA to assess tumor dynamics. Nat Med 14:985-990. -- ctDNA half-life ~114 min; molecule-counting framing of tumor dynamics.
  • Schmitt MW, Kennedy SR, Salk JJ, et al. 2012. Detection of ultra-rare mutations by next-generation sequencing. PNAS 109:14508-14513. -- Duplex sequencing; theoretical error floor <1 per 1e9 nt.
  • Newman AM, Bratman SV, To J, et al. 2014. An ultrasensitive method for quantitating circulating tumor DNA with broad patient coverage. Nat Med 20:548-554. -- CAPP-Seq; UMI-consensus error suppression.
  • Newman AM, Lovejoy AF, Klass DM, et al. 2016. Integrated digital error suppression for improved detection of circulating tumor DNA. Nat Biotechnol 34:547-555. -- iDES; ~3-15x gain; ctDNA to ~4e-5.
  • Razavi P, Li BT, Brown DN, et al. 2019. High-intensity sequencing reveals the sources of plasma circulating cell-free DNA variants. Nat Med 25:1928-1937. -- CHIP as the dominant non-tumor signal in the LoB blank.
  • Adalsteinsson VA, Ha G, Freeman SS, et al. 2017. Scalable whole-exome sequencing of cell-free DNA reveals high concordance with metastatic tumors. Nat Commun 8:1324. -- ichorCNA; copy-number tumor-fraction floor ~3%.
  • Reinert T, Henriksen TV, Christensen E, et al. 2019. Analysis of plasma cell-free DNA by ultradeep sequencing in patients with stages I to III colorectal cancer. JAMA Oncol 5:1124-1131. -- Signatera; 16-variant integration; >=2-of-N positivity.
  • Fang LT, Zhu B, Zhao Y, et al.; SEQC2 Consortium. 2021. Establishing community reference samples, data and call sets for benchmarking cancer mutation detection using whole-genome sequencing. Nat Biotechnol 39:1151-1160. -- SEQC2 Sample A / HCC1395 contrived reference standards.
  • CLSI EP17-A2. 2012. Evaluation of Detection Capability for Clinical Laboratory Measurement Procedures; Approved Guideline -- Second Edition. Clinical and Laboratory Standards Institute. -- Governing LoB/LoD/LoQ definitions.
  • ctdna-mutation-detection - applies these limits to low-VAF somatic calls
  • longitudinal-monitoring - per-timepoint LoD and left-censoring of undetectable samples
  • tumor-fraction-estimation - the ~3% CNA-based detection floor as an LoD
  • experimental-design/multiple-testing - repeated-surveillance specificity and FDR
  • clinical-biostatistics/power-and-sample-size - validation-study design

© 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/analytical-validation of GPTomics/bioSkills.

  • SKILL.md
  • examples/detection_limits.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 Analytical Validation 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 Analytical Validation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bio Analytical Validation this skillGPTomics/bioSkills1.2k1 repos~4.2kAutomated safety check: PassMIT
Dbsnp Databasegoogle-deepmind/science-skills3.2k3 repos~3.4kAutomated safety check: NotesApache-2.0
Metabolic Study Planneraiming-lab/AutoResearchClaw15k—~1.9kAutomated safety check: PassMIT
13C Metabolic Flux AnalysisK-Dense-AI/scientific-agent-skills48k1 repos~3.2kAutomated safety check: PassMIT
Alphagenome Single Variant Analysisgoogle-deepmind/science-skills3.2k2 repos~3kAutomated safety check: NotesApache-2.0
MFA Pipeline Orchestratoraiming-lab/AutoResearchClaw15k—~923Automated safety check: PassMIT

Similar skills

  • Dbsnp Database

    google-deepmind/science-skills

    A skill your agent uses when you want to look up, map, and search for short genetic variants (SNPs, indels) in NCBI's dbSNP database.

    3.2k GitHub starsUsed in 3 repos~3.4k tokens
    Research & ScienceAuto-check: notes
  • Metabolic Study Planner

    aiming-lab/AutoResearchClaw

    Turns a broad metabolic modelling topic into a concrete, paper-shaped plan with organism, model, perturbations, metrics and figures before any FBA code is written.

    15k GitHub stars~1.9k tokensUpdated 1 mo ago
    Research & ScienceAuto-check passed
  • 13C Metabolic Flux Analysis

    K-Dense-AI/scientific-agent-skills

    Estimates reaction fluxes inside cells from steady-state carbon-13 labeling data with a bundled mfapy-based solver, and reports which fluxes the data pin down.

    48k GitHub starsUsed in 1 repo~3.2k tokens
    Research & ScienceAuto-check passed
  • Alphagenome Single Variant Analysis

    google-deepmind/science-skills

    Analyzes genetic variant effects on gene expression (RNA-seq), chromatin accessibility (DNASE), histone marks (ChIP), and transcription factors using the AlphaGenome API.

    3.2k GitHub starsUsed in 2 repos~3k tokens
    Research & ScienceAuto-check: notes
  • MFA Pipeline Orchestrator

    aiming-lab/AutoResearchClaw

    Runs a metabolic flux analysis from model loading to phenotype prediction and figures by handing work to four sub-agents in sequence.

    15k GitHub stars~923 tokensUpdated 1 mo ago
    Research & ScienceAuto-check passed
  • Singlecell Qc

    xuzhougeng/wisp-science

    A skill your agent uses when designing, reviewing, or implementing single-cell RNA-seq QC in Python or R with a human-in-the-loop, data-driven approach.

    1k GitHub stars~1.6k tokensUpdated yesterday
    Research & ScienceAuto-check passed

More from GPTomics/bioSkills

All 552 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
  • 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
  • Bio Alignment Sorting

    GPTomics/bioSkills

    Sort alignment files by coordinate or read name using samtools and pysam.

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

Questions about Bio Analytical Validation

What does Bio Analytical Validation do?

Treats a ctDNA assay as a molecule-counting experiment at the Poisson edge and builds its analytical-validation case the measurement-science way. Bio Analytical Validation is an agent skill from GPTomics/bioSkills. Treats a ctDNA assay as a molecule-counting experiment at the Poisson edge and builds its analytical-validation case the measurement-science way.

When should I use Bio Analytical Validation?

Bio Analytical Validation fits situations like: trusting a sensitivity claim; designing a dilution-series validation; deciding how many genome equivalents are needed at a target VAF; choosing a single-locus vs panel-integrated LoD.

How do I install Bio Analytical Validation in Claude Code?

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

How do I install Bio Analytical Validation in Codex?

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

Can I use Bio Analytical Validation 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-analytical-validation -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-analytical-validation, .gemini/skills/bio-analytical-validation, .github/skills/bio-analytical-validation and .opencode/skills/bio-analytical-validation in your project.

What does Bio Analytical Validation need to run?

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

Does Bio Analytical Validation 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 Analytical Validation 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 Analytical Validation use?

Bio Analytical Validation 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 Analytical Validation use?

About 4.2k tokens (SKILL.md is roughly 17k 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 Analytical Validation?

Skills that share tags, products or a category with Bio Analytical Validation: Dbsnp Database (google-deepmind/science-skills, 3.2k stars), Metabolic Study Planner (aiming-lab/AutoResearchClaw, 15k stars), 13C Metabolic Flux Analysis (K-Dense-AI/scientific-agent-skills, 48k stars) and Alphagenome Single Variant Analysis (google-deepmind/science-skills, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bio Analytical Validation?

GPTomics (a GitHub organization) maintains it in GPTomics/bioSkills, which has 1,215 GitHub stars. The repository holds 552 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.