返回技能列表

troubleshoot-separation

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

关于

This skill provides a systematic troubleshooting framework for diagnosing and resolving chromatographic separation issues in GC and HPLC systems. It guides users through documenting symptoms, identifying root causes for peak anomalies, and implementing targeted fixes using a controlled, one-variable-at-a-time approach. Developers can use it to build or enhance applications that require structured analytical method troubleshooting.

快速安装

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 中复制并粘贴此命令以安装该技能

技能文档

分離問題のトラブルシューティング

Systematic diagnosis and resolution of GC and HPLC separation problems covering symptom documentation, peak shape diagnosis, retention anomaly investigation, matrix effect evaluation, and verified corrective action using controlled single-variable changes.

使用タイミング

  • Peaks are tailing, fronting, splitting, or broader than expected
  • Retention times have shifted or become irreproducible
  • Resolution between critical pairs has degraded
  • Baseline drift, ghost peaks, or negative peaks have appeared
  • Sensitivity has dropped or signal-to-noise has worsened
  • A method that previously worked is now failing system suitability

入力

Required

  • Problem chromatogram: Current data showing the issue
  • Reference chromatogram: Recent good chromatogram from the same method for comparison
  • Method conditions: Column, mobile phase/carrier gas, temperature/gradient, detector, flow rate
  • System log: Recent maintenance, column changes, mobile phase preparations, instrument events

Optional

  • Blank chromatogram: Most recent blank or solvent injection
  • System suitability trend data: Historical values for tailing, resolution, plates, retention time
  • Column history: Number of injections, types of samples, age of column
  • Instrument maintenance log: Pump seal replacements, lamp hours, detector service dates

手順

ステップ1: Document the Problem

  1. Describe the symptom precisely: which peaks are affected, how do they differ from the reference chromatogram.
  2. Determine when the problem started: gradual degradation or sudden onset.
  3. Record whether the problem affects all peaks or only specific ones.
  4. Note whether the problem is present in standards, samples, or both.
  5. Collect the current system suitability data and compare to historical trends.
  6. Photograph or export the problem chromatogram alongside the reference for side-by-side comparison.

期待結果: A documented problem statement with timeline, scope (all peaks vs. specific peaks, standards vs. samples), and comparison to reference data.

失敗時: If no reference chromatogram is available, inject a fresh standard preparation under the documented method conditions to establish a current baseline before troubleshooting.

ステップ2: Diagnose Peak Shape Issues

Use the symptom table to identify likely root causes.

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 the observed symptom(s) to the table above.
  2. Narrow the list of causes by checking whether the problem affects all peaks or specific ones, and whether it appeared suddenly or gradually.
  3. Prioritize the most likely cause based on the system history (recent changes, column age, maintenance status).

期待結果: One or two most-likely root causes identified from the symptom-cause mapping, prioritized by system history.

失敗時: If the symptom does not match any row in the table, or multiple symptoms are present simultaneously, the problem may be compound (e.g., column degradation plus a leak). Address the most obvious issue first, then re-evaluate.

ステップ3: Diagnose Retention Time Issues

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. Determine whether retention shifts are uniform (all peaks) or selective (specific peaks).
  2. Uniform shifts point to systematic causes (flow, temperature, mobile phase composition).
  3. Selective shifts point to column chemistry changes or specific analyte-related issues.
  4. Check the instrument pressure trace: sudden pressure changes indicate leaks or blockages.
  5. Re-inject the reference standard to confirm whether the issue is in the system or the sample.

期待結果: Root cause of retention anomaly identified and categorized as systematic (instrument/mobile phase) or column-related.

失敗時: If re-injecting the standard on a new column resolves the issue, the original column is the problem. If the issue persists on a new column, the cause is upstream (mobile phase, instrument, or method parameters).

ステップ4: Evaluate Matrix Effects

  1. Compare the standard chromatogram to the sample chromatogram:
    • Are there additional peaks in the sample that are absent in the standard?
    • Is the baseline elevated or noisy in specific retention windows?
    • Are analyte peak shapes different in the sample vs. standard (broader, tailing more)?
  2. For LC-MS: evaluate ion suppression/enhancement:
    • Post-column infusion test: infuse analyte continuously while injecting a blank matrix extract; dips in the analyte signal indicate ion suppression regions.
    • If analyte retention time coincides with a suppression region, modify the method to shift analyte elution.
  3. Check for column contamination:
    • Inject solvent blanks after a sample sequence; persistent peaks indicate column contamination.
    • Flush the column with strong solvent (100% organic for RP, or as recommended by column manufacturer).
  4. Assess sample preparation:
    • Dirty injector (autosampler needle, injection port liner in GC): replace or clean.
    • Insufficient sample cleanup: add a filtration, SPE, or protein precipitation step.
  5. For GC: check for non-volatile residue buildup in the inlet liner, which causes peak tailing and ghost peaks over time.

期待結果: Matrix effects characterized (presence/absence of interferents, ion suppression zones for LC-MS, column contamination status) with actionable recommendations.

失敗時: If matrix effects cannot be adequately characterized with available data, prepare a matrix-matched calibration curve and compare slopes to a solvent calibration curve. A slope difference > 15% indicates significant matrix effects requiring method modification.

ステップ5: Implement and Verify the Fix

  1. Change only one variable at a time. Document what was changed and why.
  2. After each change, re-inject the system suitability standard and compare to the reference chromatogram.
  3. Sequence of changes to try (from least to most disruptive):
    • Prepare fresh mobile phase / carrier gas tank
    • Replace consumables (septum, liner, frit, inline filter, lamp)
    • Tighten or replace fittings and tubing
    • Flush/regenerate the column
    • Adjust method parameters (temperature, flow, gradient, pH)
    • Replace the column
    • Service the instrument (pump seals, check valves, detector)
  4. Once the fix is identified, run the full system suitability test (n >= 5 injections).
  5. Compare all parameters (retention time, area, resolution, tailing, plates) to historical specification.
  6. Document the root cause, corrective action, and verification results in the instrument/column logbook.
  7. If the same problem recurs, establish a preventive maintenance schedule to address the root cause proactively.

期待結果: Problem resolved with system suitability parameters restored to specification. Root cause, corrective action, and verification documented.

失敗時: If all single-variable changes fail to resolve the issue, the problem may involve multiple simultaneous failures. Replace all consumables and the column together, verify with a fresh standard, and rebuild the troubleshooting from the new baseline. If the problem persists after total consumable replacement, escalate to instrument service.

バリデーション

  • Problem documented with symptom description, timeline, and scope
  • Root cause identified using symptom-cause mapping tables
  • Only one variable changed at a time during troubleshooting
  • Fix verified by system suitability test (n >= 5 replicate injections)
  • All system suitability parameters restored to within specification
  • Root cause and corrective action documented in logbook
  • Preventive measure identified to avoid recurrence

よくある落とし穴

  • Changing multiple variables simultaneously: Makes it impossible to identify the actual root cause. Always change one thing, test, then decide whether to change another.
  • Replacing the column as the first step: Column replacement is expensive and may mask the real problem (e.g., a leak, wrong mobile phase, or contaminated inlet). Exhaust simpler possibilities first.
  • Ignoring the instrument logbook: Many problems trace back to a recent maintenance event, mobile phase batch change, or column swap. Always check what changed recently.
  • Blaming the sample without evidence: Run the reference standard first. If the standard also shows the problem, the issue is in the system, not the sample.
  • Flushing a column with incompatible solvents: Never flush a reversed-phase column with pure water (causes phase collapse) or a silica HILIC column with pure aqueous buffer (irreversible damage). Follow the manufacturer's washing protocol.
  • Not documenting what was tried: Failed troubleshooting attempts are valuable information. Record every change attempted and its outcome to avoid repeating unsuccessful fixes and to build institutional knowledge.

関連スキル

  • interpret-chromatogram -- understanding the chromatographic data that reveals separation problems
  • develop-gc-method -- GC method development, relevant when troubleshooting requires method redesign
  • develop-hplc-method -- HPLC method development, relevant when troubleshooting requires method redesign
  • validate-analytical-method -- re-validation may be required after significant method changes during troubleshooting

GitHub 仓库

pjt222/agent-almanac
路径: i18n/ja/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节点的正确返回格式、数据访问方法和常见陷阱解决方案。

查看技能