返回技能列表

troubleshoot-separation

pjt222
更新于 2 days ago
4 次查看
17
2
17
在 GitHub 上查看
文档word

关于

This Claude Skill systematically diagnoses and resolves GC and HPLC chromatographic separation issues. It helps document symptoms, identify root causes for peak shape and retention anomalies, and evaluate matrix effects. Developers should use it to implement targeted fixes via a structured, one-variable-at-a-time approach.

快速安装

Claude Code

推荐
主要方式
npx skills add pjt222/agent-almanac -a claude-code
插件命令备选方式
/plugin add https://github.com/pjt222/agent-almanac
Git 克隆备选方式
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/troubleshoot-separation

在 Claude Code 中复制并粘贴此命令以安装该技能

技能文档

Troubleshoot Chromatographic Separation

GC/HPLC sep diagnosis → symptom doc → peak shape diag → retention anomaly → matrix effects → verified fix via one-var-at-time.

Use When

  • Peaks tail|front|split|broaden
  • Retention shifted|irreproducible
  • Resolution between critical pairs degraded
  • Baseline drift|ghost peaks|negative peaks
  • Sensitivity drop|S/N worse
  • Working method now fails sys suitability

In

Required

  • Problem chromatogram: Current data → issue
  • Reference chromatogram: Recent good, same method → compare
  • Method conditions: Column, mobile phase|carrier gas, temp|gradient, detector, flow
  • System log: Recent maint, col changes, mobile phase prep, instrument events

Optional

  • Blank chromatogram: Most recent blank|solvent inj
  • Sys suitability trends: Historical tailing, resolution, plates, RT
  • Col history: # injections, sample types, age
  • Instrument maint log: Pump seal, lamp hrs, detector service

Do

Step 1: Doc Problem

  1. Symptom precise: which peaks, how differ from ref
  2. When started: gradual|sudden
  3. All peaks or specific?
  4. Standards|samples|both?
  5. Current sys suitability vs historical
  6. Photo|export problem chromatogram side-by-side w/ ref

Got: Problem statement w/ timeline, scope (all|specific peaks, std|sample), ref comparison.

If err: No ref → inject fresh standard prep under documented method → establish current baseline before troubleshoot.

Step 2: Diag Peak Shape

SymptomPossible CausesSolutions
Tailing (T > 1.5)Secondary interactions (silanol activity), dead volume in fittings, contaminated column frit, overloaded active sitesAdd amine modifier (HPLC), deactivate liner (GC), replace frit, trim column inlet, reduce injection mass
Fronting (T < 0.8)Column overload (mass or volume), mismatch between sample solvent and mobile phase strengthReduce injection volume or concentration, dilute in weaker solvent, use larger-bore column
Split / double peaksPartially blocked frit, void at column head, two polymorphic forms, isomeric interconversionReplace frit, repack column head, verify sample stability, adjust pH to lock one form
Broad peaks (all)Extra-column band broadening, wrong tubing ID, large detector cell, old column, low plate countMinimize post-column tubing length and ID, check connections, replace column
Broad peaks (early eluters)Poor focusing at column head, injection solvent too strong (HPLC), cold on-column (GC)Use weaker injection solvent, reduce injection volume, increase initial oven temp
Broad peaks (late eluters)On-column diffusion, temperature too low (GC), insufficient gradient steepness (HPLC)Increase final oven temperature, steepen gradient, add organic wash
Negative peaksSample solvent refractive index/absorbance differs from mobile phase, vacancy peaks (IEX)Match sample solvent to mobile phase, use different detection wavelength
Ghost peaksCarryover from previous injection, contaminated mobile phase, column bleed, septum bleed (GC)Run blank to confirm, clean or replace injection system, filter/degas mobile phase, replace septum
Baseline drift (upward)Column bleed (GC at high temp), gradient elution baseline shift (HPLC), lamp instability (UV)Reduce max temp, use low-bleed column (GC), run blank gradient to characterize (HPLC), replace lamp
Baseline noise (high-frequency)Electrical interference, pump pulsation, air bubbles in detector, contaminated detectorGround instrument, replace pump seals, degas mobile phase, clean detector cell
  1. Match symptom(s) → table
  2. Narrow causes: all peaks|specific, sudden|gradual
  3. Prioritize → sys history (recent changes, col age, maint)

Got: 1-2 most-likely causes from sym-cause map, prioritized by history.

If err: No table match or multi-symptom → compound problem (col degradation + leak). Address obvious first → re-eval.

Step 3: Diag Retention

SymptomPossible CausesSolutions
All peaks shifted earlierIncreased flow rate, higher column temperature, stronger mobile phase, column voidCheck flow rate setting and actual delivery, verify temperature, remake mobile phase, inspect column
All peaks shifted laterDecreased flow rate, lower column temperature, weaker mobile phase, partially blocked tubingCheck for leaks (pressure drop), verify temperature, remake mobile phase, check inline filter
Retention time drift (gradual)Column degradation, mobile phase evaporation (open reservoir), temperature fluctuationReplace column, seal reservoir, stabilize oven, use column thermostat
Retention time irreproducibleLeak at fitting, check valve malfunction, autosampler timing error, inadequate re-equilibrationPressure-test fittings, replace check valves, verify autosampler, increase equilibration volume
Lost retention (k' near 0)Phase collapse (RP at high aqueous), column dewetting, wrong mobile phase, reversed connectionsUse polar-embedded or AQ-type column, re-wet column with organic, verify mobile phase, check plumbing
Co-elution (previously resolved)Column selectivity lost (bonded phase stripped), mobile phase composition changed, temperature changedReplace column, verify mobile phase preparation, check temperature setpoint vs. actual
  1. Shifts uniform (all) or selective (specific)?
  2. Uniform → systematic (flow, temp, mobile phase)
  3. Selective → col chemistry|specific analyte
  4. Check pressure trace: sudden change → leaks|blockage
  5. Re-inject ref std → confirm sys vs sample

Got: Retention root cause categorized: systematic (instrument/MP) or col-related.

If err: Re-inject std on new col resolves → orig col = problem. Persists on new col → upstream (MP, instrument, method).

Step 4: Matrix Effects

  1. Std vs sample chromatogram:
    • Extra peaks in sample absent from std?
    • Baseline elevated|noisy in retention windows?
    • Analyte peaks differ in sample vs std (broader, more tailing)?
  2. LC-MS → ion suppression/enhancement:
    • Post-col infusion: infuse analyte continuous while inject blank matrix → dips = suppression regions
    • Analyte RT coincides w/ suppression → shift elution
  3. Col contamination:
    • Solvent blanks after sample seq → persistent peaks = col contamination
    • Flush col w/ strong solvent (100% organic for RP, or per mfr)
  4. Sample prep:
    • Dirty injector (autosampler needle, GC liner) → replace|clean
    • Insufficient cleanup → add filter, SPE, protein precipitation
  5. GC: non-volatile residue in inlet liner → causes tailing + ghost over time

Got: Matrix effects characterized (interferents, ion suppression zones for LC-MS, col contamination) w/ actions.

If err: Can't characterize → matrix-matched cal curve vs solvent cal curve. Slope diff > 15% → significant matrix effects → method mod.

Step 5: Fix + Verify

  1. One var at a time. Doc what + why.
  2. Per change → re-inject sys suitability std vs ref
  3. Sequence (least → most disruptive):
    • Fresh mobile phase | carrier gas tank
    • Replace consumables (septum, liner, frit, inline filter, lamp)
    • Tighten|replace fittings + tubing
    • Flush|regen col
    • Adjust method (temp, flow, gradient, pH)
    • Replace col
    • Service instrument (pump seals, check valves, detector)
  4. Fix found → full sys suitability test (n >= 5 injections)
  5. Compare all params (RT, area, resolution, tailing, plates) vs spec
  6. Doc root cause, action, verify in instrument|col logbook
  7. Recurs → preventive maint schedule

Got: Problem resolved, sys suitability params restored to spec. Root cause + action + verify documented.

If err: All single-var changes fail → multi simultaneous failures. Replace all consumables + col together → verify w/ fresh std → rebuild from new baseline. Persists after total replacement → escalate to instrument service.

Check

  • Problem documented w/ symptom, timeline, scope
  • Root cause via sym-cause maps
  • One var at a time
  • Fix verified by sys suitability (n >= 5 replicate inj)
  • All sys suitability params restored to spec
  • Root cause + action in logbook
  • Preventive measure ID'd

Traps

  • Multi vars at once: Can't ID root cause. One change → test → decide.
  • Col first: Expensive, masks real problem (leak, wrong MP, contaminated inlet). Exhaust simpler first.
  • Ignore logbook: Many problems → recent maint, MP batch, col swap. Check what changed.
  • Blame sample w/o evidence: Run ref std first. Std also shows problem → sys, not sample.
  • Incompatible solvents: Never flush RP w/ pure water (phase collapse) or silica HILIC w/ pure aqueous (irreversible). Per mfr protocol.
  • No documentation: Failed attempts valuable. Record every change + outcome → avoid repeat + build knowledge.

  • interpret-chromatogram — understanding chromatographic data revealing sep problems
  • develop-gc-method — GC method dev, relevant when troubleshooting requires redesign
  • develop-hplc-method — HPLC method dev, relevant when troubleshooting requires redesign
  • validate-analytical-method — re-validation may need after significant method changes

GitHub 仓库

pjt222/agent-almanac
路径: i18n/caveman-ultra/skills/troubleshoot-separation
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

相关推荐技能

railway-docs

文档

Railway Docs Skill可实时获取最新的Railway官方文档,确保回答的准确性。当开发者询问Railway功能特性、工作原理或分享docs.railway.com链接时,应优先使用此技能。它通过专门的LLM优化文档源提供最新信息,避免依赖过时记忆来回答技术问题。

查看技能

n8n-code-python

文档

该Skill为在n8n平台的Python代码节点中编写代码提供专家指导,特别适用于需要使用_input/_json/_node语法、Python标准库或了解n8n中Python限制的场景。它强调JavaScript应作为首选方案,仅当需要特定Python功能或对Python语法更熟悉时才使用Python。Skill提供了快速入门模板和关键注意事项,帮助开发者在n8n中高效编写Python代码。

查看技能

archon

文档

Archon Skill为开发者提供了基于RAG的语义搜索和项目任务管理功能,可通过REST API访问知识库。它支持文档搜索、网站爬取、文件上传和版本控制,适用于技术文档查询和项目管理场景。首次使用时需要配置Archon主机地址,建议在处理外部文档时优先使用该Skill。

查看技能

n8n-code-javascript

文档

这个Skill为n8n工作流中的JavaScript代码节点提供专业指导,涵盖数据处理、HTTP请求和日期操作等核心场景。它详细解释了如何正确使用n8n特有的`$input`/`$json`语法、`$helpers`工具以及DateTime对象,并包含关键的错误排查和模式选择建议。开发者通过该Skill能快速掌握Code节点的正确返回格式、数据访问方法和常见陷阱解决方案。

查看技能