Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Pcr Optimization

ASecurity

PCR assay optimization and troubleshooting — primer design, cycling conditions, and fixing failed reactions.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsgoreact

Works with

cli

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill pcr-optimization --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pcr Optimization?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Pcr Optimization
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-pcr-optimization/badge)](https://www.skillsdirectory.com/skills/aicodedecode-pcr-optimization)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: pcr-optimization
description: PCR assay optimization and troubleshooting — primer design, cycling conditions, and fixing failed reactions.
category: scientific
---

## Overview

pcr-optimization covers designing robust PCR assays and systematically troubleshooting failures:
primer design rules, reaction chemistry, cycling parameters, and the diagnostic logic that
distinguishes primer problems from template, enzyme, and contamination issues. Most PCR failures
are primer or template problems — this skill teaches you to determine which, quickly.

## When to use

- Designing primers: length, Tm, GC content, specificity checking.
- Setting up new assays: polymerase choice, buffer, Mg²⁺, cycling conditions.
- Troubleshooting: no product, wrong-size bands, smears, primer-dimers, non-specific
  amplification.
- qPCR: efficiency, standard curves, reference genes, MIQE basics.
- Contamination control: UNG, workflow separation, no-template controls.

## Core concepts

- **Primer design rules.** 18-25 nt; Tm 58-65°C with ≤2°C difference between primers; 40-60%
  GC; GC clamp (1-2 G/C at 3′ end, not >3); no stable secondary structures (hairpins,
  self-dimers, cross-dimers — check with design tools); 3′ end must match perfectly (mismatches
  here kill extension). Amplicon 100-1000 bp for standard PCR, 70-200 bp for qPCR.
- **Specificity checking.** BLAST primers against the target genome; check for SNPs under
  primers (especially 3′); for multiplex, check all cross-interactions. In silico PCR tools
  catch most off-target problems before you order.
- **Mg²⁺ titration.** The single most effective optimization: 1.5-4 mM typically. Too low: no
  product. Too high: non-specific bands. Titrate in 0.5 mM steps when an assay misbehaves.
- **Annealing temperature.** Start 3-5°C below the lower primer Tm; gradient PCR (spanning
  ±5°C) finds the optimum in one run. Touchdown PCR (starting high, decreasing) suppresses
  non-specific priming elegantly.
- **Polymerase choice.** Taq for routine (no proofreading); high-fidelity (Q5, Phusion,
  Pfu) for cloning/sequencing (error rate ~50x lower); hot-start for specificity (prevents
  room-temperature mispriming — the commonest fix for primer-dimers and smears).
- **Template quality.** Inhibitors (heparin, humic acids, excess EDTA), degraded DNA, and
  too much template (inhibits!) cause failures blamed on primers. Quantify (Qubit over
  NanoDrop for accuracy), check 260/280 and 260/230 ratios, and titrate template amount.
- **qPCR specifics.** Efficiency 90-110% from standard curves (slope −3.1 to −3.6); melt
  curves to confirm single products; no-template and no-RT controls mandatory; reference genes
  validated for stability in your conditions (not GAPDH by habit — test 3+ candidates with
  geNorm/NormFinder); follow MIQE reporting.
- **Contamination control.** Separate pre- and post-PCR areas; filter tips; UNG/dUTP systems
  for carryover prevention; no-template controls in every run. A positive NTC means stop and
  decontaminate — not "subtract background."

## Practical workflow

1. **Design.** Primers per rules above; in silico specificity check; order HPLC-purified for
   critical assays.
2. **Baseline reaction.** Standard conditions: hot-start polymerase, 1.5-3 mM Mg²⁺, 200 nM
   primers, annealing at Tm−3°C.
3. **Gradient optimization.** Annealing temperature gradient + Mg²⁺ titration in a matrix;
   pick the condition with strong specific band and clean NTC.
4. **Validate.** Sensitivity (limit of detection via dilution series), specificity (related
   targets, human DNA background), reproducibility (inter-run CV).
5. **Troubleshoot systematically.** No product → template/polymerase/primers (test with
   control template). Wrong bands → annealing temp/specificity. Smear → too much template,
   too many cycles, degraded DNA. Primer-dimer → hot-start, primer redesign, lower primer
   concentration.
6. **Document.** Full reaction recipe, cycling program, and validation data — the assay's
   birth certificate.

## Common pitfalls

- Blaming primers when the template is degraded or inhibited.
- Annealing temperature copied from a different primer pair.
- Too much template DNA (inhibition masquerading as failure).
- Primer-dimers "fixed" by ignoring them instead of hot-start/redesign.
- qPCR without efficiency validation or melt curves.
- Reference gene chosen by habit, not validated.
- Positive NTCs worked around instead of decontaminated.
- Excess cycles (>35) amplifying non-specific products and primer-dimers.
- Template added to master mix at the bench instead of on ice (undermining hot-start).
- Skipping gel verification of amplicon size before downstream use.
- dNTP/polymerase past expiry silently degrading reaction efficiency.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →