troubleshoot-separation
について
このスキルは、GCおよびHPLCシステムにおけるクロマトグラフィー分離の問題を診断・解決するための体系的なトラブルシューティングフレームワークを提供します。ユーザーを症状の記録、ピーク異常の根本原因の特定、そして制御された単一変数ずつのアプローチを用いた的確な修正の実施へと導きます。開発者は、構造化された分析方法のトラブルシューティングを必要とするアプリケーションの構築や強化にこれを活用できます。
クイックインストール
Claude Code
推奨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/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
- Describe the symptom precisely: which peaks are affected, how do they differ from the reference chromatogram.
- Determine when the problem started: gradual degradation or sudden onset.
- Record whether the problem affects all peaks or only specific ones.
- Note whether the problem is present in standards, samples, or both.
- Collect the current system suitability data and compare to historical trends.
- 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.
| Symptom | Possible Causes | Solutions |
|---|---|---|
| Tailing (T > 1.5) | Secondary interactions (silanol activity), dead volume in fittings, contaminated column frit, overloaded active sites | Add 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 strength | Reduce injection volume or concentration, dilute in weaker solvent, use larger-bore column |
| Split / double peaks | Partially blocked frit, void at column head, two polymorphic forms, isomeric interconversion | Replace 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 count | Minimize 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 peaks | Sample solvent refractive index/absorbance differs from mobile phase, vacancy peaks (IEX) | Match sample solvent to mobile phase, use different detection wavelength |
| Ghost peaks | Carryover 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 detector | Ground instrument, replace pump seals, degas mobile phase, clean detector cell |
- Match the observed symptom(s) to the table above.
- Narrow the list of causes by checking whether the problem affects all peaks or specific ones, and whether it appeared suddenly or gradually.
- 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
| Symptom | Possible Causes | Solutions |
|---|---|---|
| All peaks shifted earlier | Increased flow rate, higher column temperature, stronger mobile phase, column void | Check flow rate setting and actual delivery, verify temperature, remake mobile phase, inspect column |
| All peaks shifted later | Decreased flow rate, lower column temperature, weaker mobile phase, partially blocked tubing | Check for leaks (pressure drop), verify temperature, remake mobile phase, check inline filter |
| Retention time drift (gradual) | Column degradation, mobile phase evaporation (open reservoir), temperature fluctuation | Replace column, seal reservoir, stabilize oven, use column thermostat |
| Retention time irreproducible | Leak at fitting, check valve malfunction, autosampler timing error, inadequate re-equilibration | Pressure-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 connections | Use 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 changed | Replace column, verify mobile phase preparation, check temperature setpoint vs. actual |
- Determine whether retention shifts are uniform (all peaks) or selective (specific peaks).
- Uniform shifts point to systematic causes (flow, temperature, mobile phase composition).
- Selective shifts point to column chemistry changes or specific analyte-related issues.
- Check the instrument pressure trace: sudden pressure changes indicate leaks or blockages.
- 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
- 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)?
- 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.
- 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).
- 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.
- 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
- Change only one variable at a time. Document what was changed and why.
- After each change, re-inject the system suitability standard and compare to the reference chromatogram.
- 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)
- Once the fix is identified, run the full system suitability test (n >= 5 injections).
- Compare all parameters (retention time, area, resolution, tailing, plates) to historical specification.
- Document the root cause, corrective action, and verification results in the instrument/column logbook.
- 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 problemsdevelop-gc-method-- GC method development, relevant when troubleshooting requires method redesigndevelop-hplc-method-- HPLC method development, relevant when troubleshooting requires method redesignvalidate-analytical-method-- re-validation may be required after significant method changes during troubleshooting
GitHub リポジトリ
関連スキル
railway-docs
ドキュメントこのスキルは、Railwayの機能や仕様、特定のドキュメントURLに関する質問に答えるために、最新のRailwayドキュメントを取得します。開発者がRailwayの公式情報源から正確かつ最新の情報を直接受け取れるようにします。ユーザーがRailwayの動作方法について尋ねたり、Railwayドキュメントを参照する際にご利用ください。
n8n-code-python
ドキュメントこのClaudeスキルは、n8nのコードノードでPythonコードを記述するための専門的なガイダンスを提供します。具体的には、Pythonの標準ライブラリの使用方法や、`_input`、`_json`、`_node`といったn8n独自の構文の扱い方を解説します。n8n環境内におけるPythonの制限事項を開発者が理解できるよう支援し、ほとんどのワークフローではJavaScriptの使用を推奨しながらも、特定のデータ変換ニーズに対応するPythonソリューションを提案します。
archon
ドキュメントArchonスキルは、RAGを活用したセマンティック検索とプロジェクト管理をREST APIを通じて提供します。ドキュメントの検索、階層的なプロジェクト/タスクの管理、ドキュメントアップロード機能を備えたナレッジ検索の実行にご利用いただけます。外部ドキュメントを検索する際は、他の情報源を利用する前に常にArchonを最優先で使用してください。
n8n-code-javascript
ドキュメントこのClaudeスキルは、n8nのCodeノードでJavaScriptコードを書くための専門的なガイダンスを提供します。`$input`/`$json`変数、HTTPヘルパー、DateTime処理などの重要なn8n固有の構文を網羅し、一般的なエラーのトラブルシューティングも行います。CodeノードでカスタムJavaScript処理を必要とするn8nワークフローを開発する際にご利用ください。
