Back to Skills

develop-gc-method

pjt222
Updated 2 days ago
6 views
17
2
17
View on GitHub
Developmentgeneral

About

This Claude Skill helps developers create a gas chromatography method from scratch, guiding them through column selection, temperature programming, and detector configuration. It's designed for setting up new analyses or adapting existing methods to different instruments or sample matrices. The skill performs initial performance validation for volatile and semi-volatile target compounds.

Quick Install

Claude Code

Recommended
Primary
npx skills add pjt222/agent-almanac -a claude-code
Plugin CommandAlternative
/plugin add https://github.com/pjt222/agent-almanac
Git CloneAlternative
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/develop-gc-method

Copy and paste this command in Claude Code to install this skill

Documentation

Develop a GC Method

Systematic GC method dev: column pick + temp program + carrier + detector + initial perf check for volatile/semi-volatile analytes.

Use When

  • New GC for volatile/semi-volatile compounds
  • Adapt published method → different instrument/matrix
  • Replace existing method failing perf
  • Method for compounds w/ known bp + polarity
  • Packed → capillary transition

In

Required

  • Target analytes: Compounds + CAS + MW + bp
  • Sample matrix: Sample type (air, water extract, solvent, bio fluid)
  • Detection limits: LOD/LOQ per analyte

Optional

  • Reference method: Published (EPA, ASTM, pharmacopeial) → start
  • Available columns: On-hand inventory
  • Instrument config: GC model, detectors, autosampler
  • Throughput: Max run time/sample
  • Regulatory: GLP, GMP, EPA, etc

Do

Step 1: Analytical Objectives

  1. List analytes + props (bp, polarity, MW).
  2. ID matrix + expected interferents/co-extractives.
  3. Specify LOD/LOQ, quant range, Rs for critical pairs.
  4. Method must meet regulatory (EPA 8260, USP, etc)?
  5. Doc throughput: max run time, inj vol, prep constraints.

→ Written spec: analytes + matrix + limits + Rs + regulatory/throughput.

If err: volatility data missing → estimate bp from structural analogs or scout run on mid-polarity col for elution order.

Step 2: Pick Column

Dimensions + phase via analyte polarity + separation diff.

Column TypeStationary PhasePolarityTypical Use Cases
DB-1 / HP-1100% dimethylpolysiloxaneNon-polarHydrocarbons, solvents, general screening
DB-5 / HP-55% phenyl-methylpolysiloxaneLow polaritySemi-volatiles, EPA 8270, drugs of abuse
DB-170114% cyanopropylphenylMid polarityPesticides, herbicides
DB-WAX / HP-INNOWaxPolyethylene glycolPolarAlcohols, fatty acids, flavors, essential oils
DB-6246% cyanopropylphenylMid polarityVolatile organics, EPA 624/8260
DB-FFAPModified PEG (nitroterephthalic acid)Highly polarOrganic acids, free fatty acids
DB-3535% phenyl-methylpolysiloxaneMid-low polarityPolychlorinated biphenyls, confirmatory column
  1. Analyte polarity ↔ phase: like dissolves like.
  2. Length (15-60 m): longer → more plates, longer runs.
  3. ID (0.25-0.53 mm): narrower → better eff, wider → more capacity.
  4. Film (0.25-5.0 um): thicker → retain volatiles longer.
  5. Complex matrices → guard col or retention gap.

→ Col spec (phase + L + ID + film) justified by analyte + Rs reqs.

If err: no single col resolves all → confirm col w/ orthogonal selectivity (DB-1 primary, DB-WAX confirm).

Step 3: Optimize Temp Program

  1. Initial oven ≤ bp of most volatile (hold 1-2 min → solvent focus).
  2. Linear ramp starts:
    • Simple: 10-20 C/min
    • Complex: 3-8 C/min (better Rs)
    • Ultra-fast: 25-40 C/min on short thin-film
  3. Final temp 10-20 C above bp of least volatile.
  4. Final hold 2-5 min → full elution + bake-out.
  5. Co-eluting critical pairs → isothermal hold before elution, or slower ramp there.
  6. Verify total run time meets throughput.

→ Temp program (init + hold + ramp + final + hold) separates all targets in acceptable time.

If err: critical pairs still unresolved after ramp → revisit col (Step 2) or multi-ramp w/ slower rates in problem region.

Step 4: Pick Carrier Gas

PropertyHelium (He)Hydrogen (H2)Nitrogen (N2)
Optimal linear velocity20-40 cm/s30-60 cm/s10-20 cm/s
Efficiency at high flowGoodBest (flat van Deemter)Poor
Speed advantageBaseline1.5-2x faster than HeSlowest
SafetyInertFlammable (needs leak detection)Inert
Cost / availabilityExpensive, supply concernsLow cost, generator optionVery low cost
Detector compatibilityAll detectorsNot with ECD; caution with some MSAll detectors
  1. Default He for general + regulatory methods specifying He.
  2. H2 for faster or when He supply constrained; install H2 leak detection + interlocks.
  3. N2 only for simple separations or when cost primary.
  4. Flow → optimal linear velocity for gas + col ID.
  5. Measure actual velocity via unretained (e.g., methane on FID).

→ Carrier picked + flow at optimal velocity, verified by unretained peak.

If err: eff lower than expected → van Deemter curve (plate height vs velocity) over 5-7 flows for true optimum.

Step 5: Pick Detector

DetectorSelectivitySensitivity (approx.)Linear RangeBest For
FIDC-H bonds (universal organic)Low pg C/s10^7Hydrocarbons, general organics, quantitation
TCDUniversal (all compounds)Low ng10^5Permanent gases, bulk analysis
ECDElectronegative groups (halogens, nitro)Low fg (Cl compounds)10^4Pesticides, PCBs, halogenated solvents
NPD/FPDN, P (NPD); S, P (FPD)Low pg10^4-10^5Organophosphorus pesticides, sulfur compounds
MS (EI)Structural identificationLow pg (scan), fg (SIM)10^5-10^6Unknowns, confirmation, trace analysis
MS/MSHighest selectivityfg range10^5Complex matrices, ultra-trace, forensic
  1. Match detector to analyte chem + sensitivity.
  2. Quant in simple matrices → FID default (robust + linear + low maint).
  3. Trace in complex matrices → MS SIM or MS/MS MRM.
  4. Halogenated at trace → ECD best sensitivity.
  5. Detector temp 20-50 C above max oven → prevent condensation.
  6. Optimize detector gas flows per mfr.

→ Detector picked + config w/ temps + flows for targets.

If err: sensitivity insufficient → concentrate sample (bigger inj, solvent evap) or more sensitive/selective detector.

Step 6: Validate Initial Perf

  1. System suitability std: all targets at mid-range conc.
  2. Inject std 6× consec.
  3. Evaluate:
    • RT RSD: < 1.0%
    • Peak area RSD: < 2.0% (< 5.0% trace)
    • Rs critical pairs: ≥ 1.5 (baseline) or ≥ 2.0 regulated
    • Tailing factor: 0.8-1.5 (USP T ≤ 2.0)
    • Theoretical plates N: vs col mfr spec
  4. Blank inj → no carryover/ghost peaks.
  5. Matrix blank → ID interferents at target RT.
  6. Doc all in method summary.

→ Suitability met across replicates, no carryover/matrix interference at target windows.

If err: tailing → check active sites (recondition, trim 0.5 m inlet, replace liner). RSD high → autosampler precision + inj technique. Rs low → Step 3 temp refinement.

Check

  • All targets Rs ≥ 1.5 critical pairs
  • RT RSD < 1.0% over 6 reps
  • Peak area RSD < 2.0% over 6 reps
  • Tailing 0.8-1.5 all analytes
  • Blank no carryover >0.1% working conc
  • Matrix blank no interference at targets
  • Run time meets throughput
  • All params documented (col, temps, flows, detector)

Traps

  • Column bleed temp limit: Above max isothermal → elevated baseline + ghost peaks + col degradation. Check spec sheet.
  • Oversized inj: Too much solvent → fronting + poor Rs early. Match inj vol to col capacity (0.5-2 uL for 0.25 mm ID split).
  • Wrong liner: Splitless → single/double-taper deactivated; split → w/ glass wool. Mismatch → poor repro.
  • Septum/liner maint: Coring + contamination = top sources of ghost peaks + tailing. Septa every 50-100 inj, liners scheduled.
  • Skip van Deemter: Mfr default flow not measured optimum → wasted eff, esp carrier gas swaps.
  • Insufficient conditioning: New cols → condition (ramp to max temp under carrier, no detector) to clear mfr residues.

  • develop-hplc-method — LC method dev for non-volatile/thermally labile
  • interpret-chromatogram — reading GC + HPLC chromatograms
  • troubleshoot-separation — diagnose peak shape/RT/Rs problems
  • validate-analytical-method — formal ICH Q2 valid. of GC method

GitHub Repository

pjt222/agent-almanac
Path: i18n/caveman-ultra/skills/develop-gc-method
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

Related Skills

qmd

Development

qmd is a local search and indexing CLI tool that enables developers to index and search through local files using hybrid search combining BM25, vector embeddings, and reranking. It supports both command-line usage and MCP (Model Context Protocol) mode for integration with Claude. The tool uses Ollama for embeddings and stores indexes locally, making it ideal for searching documentation or codebases directly from the terminal.

View skill

subagent-driven-development

Development

This skill executes implementation plans by dispatching a fresh subagent for each independent task, with code review between tasks. It enables fast iteration while maintaining quality gates through this review process. Use it when working on mostly independent tasks within the same session to ensure continuous progress with built-in quality checks.

View skill

mcporter

Development

The mcporter skill enables developers to manage and call Model Context Protocol (MCP) servers directly from Claude. It provides commands to list available servers, call their tools with arguments, and handle authentication and daemon lifecycle. Use this skill for integrating and testing MCP server functionality in your development workflow.

View skill

adk-deployment-specialist

Development

This skill deploys and orchestrates Vertex AI ADK agents using A2A protocol, managing AgentCard discovery, task submission, and supporting tools like Code Execution Sandbox and Memory Bank. It enables building multi-agent systems with sequential, parallel, or loop orchestration patterns in Python, Java, or Go. Use it when asked to deploy ADK agents or orchestrate agent workflows on Google Cloud.

View skill