develop-gc-method
À propos
Cette compétence Claude aide les développeurs à créer des méthodes de chromatographie en phase gazeuse à partir de zéro en guidant la sélection des colonnes, la programmation de température et la configuration des détecteurs. Elle est conçue pour démarrer de nouvelles analyses CPG ou adapter des méthodes existantes à différents instruments. La compétence prend en charge les composés volatils et semi-vololatis et inclut une validation initiale des performances.
Installation rapide
Claude Code
Recommandénpx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/develop-gc-methodCopiez et collez cette commande dans Claude Code pour installer cette compétence
Documentation
Develop a GC Method
Build gas chromatography method step-by-step. Column choice, temp program, carrier gas + detector, initial perf check. Volatile + semi-volatile analytes.
When Use
- Start new GC analysis for volatile or semi-volatile compounds
- Adapt published method to different instrument or matrix
- Replace existing method that no longer meets perf needs
- Develop method for compounds with known boiling points + polarities
- Move from packed-column to capillary method
Inputs
Required
- Target analytes: Compound list with CAS numbers, molecular weights, boiling points
- Sample matrix: Sample type (air, water extract, solvent solution, biological fluid)
- Detection limits: Required LOD/LOQ per analyte
Optional
- Reference method: Published method (EPA, ASTM, pharmacopeial) as starting point
- Available columns: Column inventory on hand
- Instrument config: GC model, available detectors, autosampler type
- Throughput needs: Max run time per sample
- Regulatory framework: GLP, GMP, EPA, or other compliance context
Steps
Step 1: Define Analytical Objectives
- List all target analytes + physical properties (boiling point, polarity, molecular weight).
- Identify sample matrix + expected interferents or co-extractives.
- Set required detection limits, quantitation range, acceptable resolution between critical pairs.
- Decide if method must meet regulatory standard (EPA 8260, USP, etc.).
- Document throughput needs: max run time, injection volume, sample prep constraints.
Got: Written spec lists analytes, matrix, detection limits, resolution needs, regulatory/throughput constraints.
If fail: Analyte volatility data unavailable? Estimate boiling points from structural analogs or do scouting run on mid-polarity column to establish elution order.
Step 2: Pick Column
Pick column dimensions + stationary phase by analyte polarity + separation difficulty.
| Column Type | Stationary Phase | Polarity | Typical Use Cases |
|---|---|---|---|
| DB-1 / HP-1 | 100% dimethylpolysiloxane | Non-polar | Hydrocarbons, solvents, general screening |
| DB-5 / HP-5 | 5% phenyl-methylpolysiloxane | Low polarity | Semi-volatiles, EPA 8270, drugs of abuse |
| DB-1701 | 14% cyanopropylphenyl | Mid polarity | Pesticides, herbicides |
| DB-WAX / HP-INNOWax | Polyethylene glycol | Polar | Alcohols, fatty acids, flavors, essential oils |
| DB-624 | 6% cyanopropylphenyl | Mid polarity | Volatile organics, EPA 624/8260 |
| DB-FFAP | Modified PEG (nitroterephthalic acid) | Highly polar | Organic acids, free fatty acids |
| DB-35 | 35% phenyl-methylpolysiloxane | Mid-low polarity | Polychlorinated biphenyls, confirmatory column |
- Match analyte polarity to stationary phase: like dissolves like.
- Pick column length (15-60 m): longer = more plates, longer run.
- Pick inner diameter (0.25-0.53 mm): narrower = better efficiency, wider = more capacity.
- Pick film thickness (0.25-5.0 um): thicker films retain volatile analytes longer.
- Complex matrices? Consider guard column or retention gap.
Got: Column spec (phase, length, ID, film thickness) justified by analyte properties + separation needs.
If fail: No single column resolves all critical pairs? Plan confirmation column with orthogonal selectivity (e.g., DB-1 primary, DB-WAX confirmatory).
Step 3: Optimize Temperature Program
- Set initial oven temp at or below boiling point of most volatile analyte (hold 1-2 min for solvent focusing).
- Apply linear ramp. Starting points:
- Simple mixtures: 10-20 C/min
- Complex mixtures: 3-8 C/min for better resolution
- Ultra-fast screening: 25-40 C/min on short thin-film columns
- Set final temp 10-20 C above boiling point of least volatile analyte.
- Add final hold (2-5 min) for complete elution + column bake-out.
- Critical pairs co-elute? Insert isothermal hold just before elution, or reduce ramp rate in that region.
- Verify total run time meets throughput needs.
Got: Temp program (initial temp, hold, ramp rate(s), final temp, final hold) separates all target analytes within acceptable run time.
If fail: Critical pairs still not resolved after ramp opt? Revisit column selection (Step 2) or try multi-ramp program with slower rates in problem region.
Step 4: Pick Carrier Gas
| Property | Helium (He) | Hydrogen (H2) | Nitrogen (N2) |
|---|---|---|---|
| Optimal linear velocity | 20-40 cm/s | 30-60 cm/s | 10-20 cm/s |
| Efficiency at high flow | Good | Best (flat van Deemter) | Poor |
| Speed advantage | Baseline | 1.5-2x faster than He | Slowest |
| Safety | Inert | Flammable (needs leak detection) | Inert |
| Cost / availability | Expensive, supply concerns | Low cost, generator option | Very low cost |
| Detector compatibility | All detectors | Not with ECD; caution with some MS | All detectors |
- Default to helium for general work + regulatory methods specifying He.
- Consider hydrogen for faster analysis or when helium constrained. Install hydrogen-specific leak detection + safety interlocks.
- Use nitrogen only for simple separations or cost-driven work.
- Set carrier gas flow to optimal linear velocity for gas + column ID.
- Measure actual linear velocity with unretained compound (e.g., methane on FID).
Got: Carrier gas picked, flow at optimal linear velocity, verified via unretained peak measurement.
If fail: Efficiency lower than expected at set flow? Generate van Deemter curve (plate height vs linear velocity) using 5-7 flow rates to find true optimum.
Step 5: Pick Detector
| Detector | Selectivity | Sensitivity (approx.) | Linear Range | Best For |
|---|---|---|---|---|
| FID | C-H bonds (universal organic) | Low pg C/s | 10^7 | Hydrocarbons, general organics, quantitation |
| TCD | Universal (all compounds) | Low ng | 10^5 | Permanent gases, bulk analysis |
| ECD | Electronegative groups (halogens, nitro) | Low fg (Cl compounds) | 10^4 | Pesticides, PCBs, halogenated solvents |
| NPD/FPD | N, P (NPD); S, P (FPD) | Low pg | 10^4-10^5 | Organophosphorus pesticides, sulfur compounds |
| MS (EI) | Structural identification | Low pg (scan), fg (SIM) | 10^5-10^6 | Unknowns, confirmation, trace analysis |
| MS/MS | Highest selectivity | fg range | 10^5 | Complex matrices, ultra-trace, forensic |
- Match detector to analyte chemistry + required sensitivity.
- Quantitative work, simple matrices → FID default (robust, linear, low maintenance).
- Trace analysis, complex matrices → MS in SIM mode or MS/MS in MRM mode.
- Halogenated compounds at trace → ECD gives best sensitivity.
- Set detector temp 20-50 C above max oven temp to stop condensation.
- Optimize detector gas flows per manufacturer.
Got: Detector picked + configured. Right temps + gas flows for target analytes.
If fail: Detector sensitivity insufficient at required detection limits? Concentrate sample (bigger injection, solvent evaporation) or switch to more sensitive/selective detector.
Step 6: Validate Initial Performance
- Prep system suitability standard with all target analytes at mid-range conc.
- Inject standard 6x consecutive.
- Evaluate:
- Retention time RSD: < 1.0%
- Peak area RSD: < 2.0% (< 5.0% for trace-level)
- Resolution between critical pairs: Rs >= 1.5 (baseline) or >= 2.0 for regulated
- Peak tailing factor: 0.8-1.5 (USP criteria T <= 2.0)
- Theoretical plates (N): verify vs column manufacturer spec
- Inject blank to confirm no carryover or ghost peaks.
- Inject matrix blank to find potential interferents at target retention times.
- Document all params in method summary sheet.
Got: System suitability criteria met for all analytes across replicate injections. No carryover or matrix interferences at target retention windows.
If fail: Tailing? Check active sites (re-condition column, trim 0.5 m from inlet end, replace liner). RSD over limits? Investigate autosampler precision + injection technique. Resolution insufficient? Return to Step 3 to refine temp program.
Checks
- All target analytes separated with Rs >= 1.5 for critical pairs
- Retention time RSD < 1.0% over 6 replicate injections
- Peak area RSD < 2.0% over 6 replicate injections
- Peak tailing factors within 0.8-1.5 for all analytes
- Blank shows no carryover > 0.1% of working conc
- Matrix blank shows no interferents at target retention windows
- Total run time meets throughput needs
- Method params fully documented (column, temps, flows, detector settings)
Pitfalls
- Ignoring column bleed temp limits: Above max isothermal temp of stationary phase → elevated baseline, ghost peaks, accelerated column degradation. Always check column spec sheet.
- Oversized injection volumes: Too much solvent → fronting peaks, poor resolution for early eluters. Match injection volume to column capacity (usually 0.5-2 uL for 0.25 mm ID in split mode).
- Wrong liner for injection mode: Splitless = single-taper or double-taper deactivated liner. Split = liner with glass wool. Mismatched liners → poor reproducibility.
- Neglecting septum + liner maintenance: Septum coring + liner contamination = most common sources of ghost peaks + tailing. Replace septa every 50-100 injections, liners on documented schedule.
- Skipping van Deemter optimization: Running at manufacturer default flow instead of measured optimum wastes efficiency, especially when switching carrier gases.
- Insufficient column conditioning: New columns must be conditioned (ramp to max temp under carrier gas flow, no detector) to remove manufacturing residues before use.
See Also
develop-hplc-method-- liquid chromatography for non-volatile or thermally labile analytesinterpret-chromatogram-- reading + interpreting GC + HPLC chromatogramstroubleshoot-separation-- diagnose + fix peak shape, retention, resolution problemsvalidate-analytical-method-- formal ICH Q2 validation of developed GC method
Dépôt GitHub
Compétences associées
qmd
Développementqmd est un outil CLI de recherche et d'indexation locale qui permet aux développeurs d'indexer et de rechercher dans des fichiers locaux en utilisant une recherche hybride combinant BM25, des embeddings vectoriels et du reranking. Il prend en charge à la fois une utilisation en ligne de commande et un mode MCP (Model Context Protocol) pour l'intégration avec Claude. L'outil utilise Ollama pour les embeddings et stocke les index localement, ce qui le rend idéal pour rechercher dans de la documentation ou des bases de code directement depuis le terminal.
subagent-driven-development
DéveloppementCette compétence exécute des plans de mise en œuvre en déployant un nouveau sous-agent pour chaque tâche indépendante, avec une revue de code entre les tâches. Elle permet une itération rapide tout en maintenant des contrôles de qualité grâce à ce processus de revue. Utilisez-la lorsque vous travaillez sur des tâches principalement indépendantes au sein d'une même session pour assurer une progression continue avec des vérifications de qualité intégrées.
mcporter
DéveloppementLa compétence mcporter permet aux développeurs de gérer et d'appeler des serveurs Model Context Protocol (MCP) directement depuis Claude. Elle fournit des commandes pour lister les serveurs disponibles, appeler leurs outils avec des arguments, et gérer l'authentification ainsi que le cycle de vie du démon. Utilisez cette compétence pour intégrer et tester les fonctionnalités des serveurs MCP dans votre flux de travail de développement.
adk-deployment-specialist
DéveloppementCette compétence déploie et orchestre des agents Vertex AI ADK en utilisant le protocole A2A, gérant la découverte d'AgentCard, la soumission de tâches, et prenant en charge des outils tels que le bac à sable d'exécution de code et la banque de mémoire. Elle permet de construire des systèmes multi-agents avec des modèles d'orchestration séquentiels, parallèles ou en boucle en Python, Java ou Go. Utilisez-la lorsqu'on vous demande de déployer des agents ADK ou d'orchestrer des flux de travail d'agents sur Google Cloud.
