Zurück zu Fähigkeiten

troubleshoot-separation

pjt222
Aktualisiert 2 days ago
3 Ansichten
17
2
17
Auf GitHub ansehen
Dokumentationword

Über

Dieses Claude-Skill diagnostiziert systematisch Probleme bei der chromatographischen Trennung in GC und HPLC und löst diese. Es hilft dabei, Symptome zu dokumentieren, Ursachen für Peakenform- und Retentionsanomalien zu identifizieren sowie Matrixeffekte zu bewerten. Entwickler sollten es nutzen, um gezielte Korrekturen durch einen strukturierten Ansatz mit jeweils einer Variablen umzusetzen.

Schnellinstallation

Claude Code

Empfohlen
Primär
npx skills add pjt222/agent-almanac -a claude-code
Plugin-BefehlAlternativ
/plugin add https://github.com/pjt222/agent-almanac
Git CloneAlternativ
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/troubleshoot-separation

Kopieren Sie diesen Befehl und fügen Sie ihn in Claude Code ein, um diese Fähigkeit zu installieren

Dokumentation

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 Repository

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

Verwandte Skills

railway-docs

Dokumentation

Diese Fähigkeit ruft aktuelle Railway-Dokumentation ab, um Fragen zu Funktionen, Funktionalität oder spezifischen Dokumentations-URLs zu beantworten. Sie stellt sicher, dass Entwickler genaue, aktuelle Informationen direkt aus den offiziellen Quellen von Railway erhalten. Nutzen Sie sie, wenn Nutzer fragen, wie Railway funktioniert oder auf Railway-Dokumentation verweisen.

Skill ansehen

n8n-code-python

Dokumentation

Dieses Claude Skill bietet fachkundige Anleitung zum Schreiben von Python-Code in n8n-Code-Nodes, insbesondere für die Verwendung der Python-Standardbibliothek und den Umgang mit n8ns spezieller Syntax wie `_input`, `_json` und `_node`. Es hilft Entwicklern, die Grenzen von Python innerhalb von n8n zu verstehen, empfiehlt JavaScript für die meisten Workflows und bietet gleichzeitig Python-Lösungen für spezifische Datenumwandlungsanforderungen.

Skill ansehen

archon

Dokumentation

Die Archon-Funktion bietet semantische Suche auf RAG-Basis und Projektmanagement über eine REST-API. Nutzen Sie sie für das Abfragen von Dokumentation, die Verwaltung hierarchischer Projekte/Aufgaben und die Durchführung von Wissenabruf mit Dokumenten-Upload-Fähigkeiten. Priorisieren Sie stets Archon zuerst bei der Suche in externer Dokumentation, bevor Sie andere Quellen verwenden.

Skill ansehen

n8n-code-javascript

Dokumentation

Diese Claude-Skill bietet fachkundige Anleitung für das Schreiben von JavaScript-Code in n8n-Code-Nodes. Sie behandelt wesentliche n8n-spezifische Syntax wie `$input`/`$json`-Variablen, HTTP-Helfer und DateTime-Verarbeitung und hilft bei der Fehlerbehebung häufiger Probleme. Nutzen Sie sie bei der Entwicklung von n8n-Workflows, die eine benutzerdefinierte JavaScript-Verarbeitung in Code-Nodes erfordern.

Skill ansehen