plugin/skills/tooluniverse-primer-design/SKILL.md
PCR / qPCR primer and oligo design — design forward/reverse primers for a target region (SantaLucia nearest-neighbor thermodynamics), compute melting temperature (Tm) and annealing temperature (Ta), check GC content, and screen an oligo for hairpins and primer-dimers. Use when you need primers for a sequence, want to QC an existing primer pair, or need the Tm of an oligo. Covers the primer-design rules (Tm matching, GC clamp, 3'-end, length) and the tools' constraint quirks.
npx skillsauth add mims-harvard/tooluniverse tooluniverse-primer-designInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Design primers for a target DNA region, get their Tm/Ta, and QC them for the secondary-structure problems that make a PCR fail.
tu run DNA_primer_design '{"operation":"primer_design",
"sequence":"ATGGCG...AACGTG", # full template; must be >= target_end + flanking primer room
"target_start":40, "target_end":125,
"tm_target":60, "product_size_min":80, "product_size_max":140}'
Returns forward_primer / reverse_primer (sequence, tm, gc_content, length, position) and product_size. (target_end is clamped to the sequence length, so a too-short template silently shrinks the target — see the constraint quirk below.)
Constraint quirk — read this or it will error.
target_start..target_endis the region the amplicon must cover, and the design only succeeds when that span fits inside the product-size window AND good-Tm primers can be placed flanking it. So you need roughly:product_size_min ≤ (target span) ≤ product ≤ product_size_max, with enough flanking sequence on both sides. Common errors and the fix:
- "Target region (N bp) is smaller than product_size_min" → your target is narrower than
product_size_min; lowerproduct_size_minor widen the target.- "product does not cover the target / does not span" → the target is too wide for
product_size_max, or runs too close to a sequence end; widenproduct_size_maxor give more flanking sequence.
tu run NEB_Tm_calculate '{"primer_sequence":"CTACCTGAAGAACCTGAG",
"primer_sequence_2":"CTTGATGTCCTCCAGCAT",
"polymerase":"Q5", "primer_concentration":500, "monovalent_salt_mm":50}'
NEB returns Tm for each primer and a recommended annealing temperature (Ta) for the chosen polymerase. IDT_analyze_oligo (sequence, salt/Mg/dNTP/oligo concentrations) adds GC%, molecular weight, and hairpin / self-dimer screening. DNA_calculate_gc_content is a quick GC check.
Tm depends on method + conditions. SantaLucia NN (the design tool), NEB, and IDT use different parameter sets, and Tm shifts with monovalent salt, Mg²⁺, and primer/dNTP concentration. Pick one calculator + condition set and use it for the whole experiment; don't compare a SantaLucia Tm to an IDT Tm. Always state the conditions.
| Property | Target | Why | |---|---|---| | Length | 18–24 nt | long enough for specificity, short enough for efficient annealing | | Tm | 58–62 °C | works with standard cycling; keep the pair within ~2–3 °C of each other | | ΔTm (forward vs reverse) | < 3 °C (≤5 absolute max) | mismatched Tm → one primer anneals poorly | | GC content | 40–60 % | balanced stability | | GC clamp | 1–2 G/C in the last 3 nt of the 3′ end | stabilizes 3′ priming; >3 G/C risks mispriming | | 3′ end | avoid 3′ complementarity within a pair and within a primer | prevents primer-dimers | | Runs / repeats | avoid ≥4 identical bases in a row and di-nucleotide repeats | reduce slippage / mispriming | | Annealing temp (Ta) | ~ Tm − 3 to −5 °C (use the polymerase's calculator) | specificity vs yield | | Amplicon (qPCR) | 70–150 bp | efficient amplification |
scripts/primer_qc.py checks a primer pair against these rules (GC clamp, 3′ self/cross-complementarity, runs, GC%, length, Wallace/NN Tm, Tm match) and flags problems — use it to QC primers from any source.
Tm and structure are necessary but not sufficient. A primer can be thermodynamically perfect and still amplify the wrong locus. These tools do not check genome specificity — always BLAST each primer (or use Primer-BLAST) against the target genome and confirm a single intended product before ordering. State this in any recommendation.
IDT_analyze_oligo / the QC script flag it.tooluniverse-sequence-analysis — upstream sequence handling (FASTQ, alignment, coverage).tooluniverse-enzyme-kinetics / tooluniverse-dose-response — other quantitative assay analyses.tools
Post-market safety surveillance and recall/adverse-event RETRIEVAL across the full spectrum of FDA-regulated products that are NOT covered by the drug-AE signal skills: medical devices, food / dietary supplements / cosmetics, veterinary drugs, and drug supply (shortages). Orchestrates openFDA endpoints (MAUDE device adverse events + device recalls + 510(k), CAERS food/supplement/ cosmetic adverse events, veterinary adverse events, drug shortages, and cross-product enforcement/recall reports). USE WHEN the user asks: "are there adverse events for [device / pacemaker / infusion pump / insulin pump]", "device recalls for [firm/product]", "supplement / vitamin / cosmetic adverse reactions", "is [drug] in shortage", "what injectables are on shortage", "veterinary / animal adverse events for [drug] in [dog/cat/horse]", "food recall for listeria", "MAUDE report for [device]", "CAERS reactions for [brand]". DO NOT USE for drug adverse-event SIGNAL detection or disproportionality (PRR / ROR / IC) or drug-AE association scoring — that is `tooluniverse-pharmacovigilance` / `tooluniverse-adverse-event-detection`. This skill is multi-product surveillance and retrieval, not drug-AE statistical signal mining.
tools
--- name: tooluniverse-phewas description: Cross-ancestry / cross-biobank phenome-wide association (PheWAS) and replication. Given ONE variant (rsID) or ONE gene, look up every phenotype it associates with across European/UK (UKB-TOPMed), Finnish (FinnGen), Japanese (BioBank Japan), and Taiwanese (TPMI) biobanks, plus exome-wide gene-burden PheWAS (Genebass), then judge whether an association replicates across ancestries or is population-specific. Use whenever the user asks "what else is this va
tools
Dereplicate a putative natural product and assign its chemical taxonomy. Use to answer "is [compound] a known natural product", "what microbe/organism produces [compound]", "what chemical class is [compound]", "dereplicate this metabolite (by formula/exact mass/InChIKey/SMILES)", or "classify this molecule into ChemOnt". Searches NPAtlas for known microbial natural products (producing organism + literature reference), assigns the ChemOnt kingdom→superclass→class→subclass hierarchy via ClassyFire, resolves systematic IUPAC names to structure via OPSIN, and cross-references identity in PubChem. NOT for general drug/compound identity or ADMET (use tooluniverse-chemical-compound-retrieval / tooluniverse-small-molecule-discovery) and NOT for metabolomics pathway/enrichment analysis (use tooluniverse-metabolomics skills).
tools
Genome-ASSEMBLY discovery, QC, and replicon mapping for any organism (bacteria, archaea, fungi, and beyond) using NCBI Datasets. Resolves an organism name or taxid to assemblies, picks the reference/representative or best-quality assembly, pulls assembly QC metrics (total length, contig/scaffold N50, contig count, GC%, assembly level, RefSeq category), enumerates chromosomes and plasmids via per-replicon sequence reports, and compares candidate assemblies on quality. Use for "what genomes are available for [organism]", "assembly stats / N50 / GC content for [GCF_/GCA_ accession]", "how many plasmids does [strain] have", "compare assemblies for [species]", "find the reference genome for [taxon]", "is this assembly Complete Genome or just contigs". NOT for gene-level orthology/synteny (use tooluniverse-comparative-genomics), plant gene structure (use tooluniverse-plant-genomics), de novo assembly from raw reads (no tool exists), or taxonomy-only name/lineage lookups.