interpret-chromatogram
정보
이 Claude Skill은 개발자를 위해 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/interpret-chromatogramClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
Interpret Chromatogram
Systematic read of GC and HPLC chromatograms. Cover system suitability, peak ID, integration, chromatographic figures, peak quality. For confident qual and quant results.
When Use
- Reviewing chromatographic data before reporting
- Verify system suitability test passes before sample sequence
- Identify unknown peaks. Confirm known analytes by retention time or spectra
- Troubleshoot unexpected peaks, baseline anomalies, integration artifacts
- Training analysts on chromatogram interpretation
Inputs
Required
- Chromatogram data: Digital or printed. Time axis + detector response axis
- Reference standard data: Retention times and responses of known analytes under same method
- Method parameters: Column, mobile phase/carrier gas, temperature/gradient, detector settings
Optional
- Spectral data: UV-Vis spectra (DAD), mass spectra (MS), other spectra for peak confirmation
- Previous chromatograms: Historical data from same method for trend compare
- System suitability criteria: Acceptance limits from method or regulatory standard
- Sample prep details: Dilution factors, extraction recovery, internal standard conc
Steps
Step 1: Verify System Suitability
Confirm chromatographic system performs within spec before interpreting sample data.
| Parameter | Typical Specification | Calculation |
|---|---|---|
| Retention time RSD | <= 1.0% | RSD of tR over n >= 5 injections |
| Peak area RSD | <= 2.0% (assay), <= 5.0% (impurity) | RSD of area over n >= 5 injections |
| Tailing factor (T) | 0.8-2.0 (USP), ideally 0.9-1.2 | T = W0.05 / (2 * f) where W0.05 = width at 5% height, f = front half-width |
| Resolution (Rs) | >= 1.5 (baseline), >= 2.0 (regulated) | Rs = 2(tR2 - tR1) / (w1 + w2) |
| Theoretical plates (N) | Per column spec (e.g., >= 2000) | N = 16(tR / w)^2 or N = 5.54(tR / w0.5)^2 |
| Capacity factor (k') | 2.0-10.0 for primary analyte | k' = (tR - t0) / t0 |
- Locate system suitability injections (usually 5-6 replicates of reference standard at start of sequence)
- Calculate each parameter from table
- Compare calculated values vs method's acceptance criteria
- Any parameter fails? System not suitable. Do not proceed until issue fixed
- Document all system suitability results in batch record
Got: All system suitability parameters within spec. System fit for purpose.
If fail: Retention time RSD fails? Check temperature stability, mobile phase prep errors, column degradation. Tailing factor fails? Inspect inlet liner (GC) or column frit (HPLC). Resolution fails? Check column with dedicated test mix, replace if needed.
Step 2: Identify Peaks
- Compare each peak's retention time (tR) vs reference standard chromatogram
- Acceptable match: within +/- 2% of reference tR (or +/- 0.1 min for short runs)
- Ambiguous IDs? Use co-injection (spiking): add reference standard to sample, re-inject. Target peak should grow without broadening or shouldering
- DAD-equipped HPLC: compare UV-Vis spectrum of each peak vs spectral library
- Spectral match index >= 990 (out of 1000) for positive ID
- Check spectral purity across peak (front, apex, tail spectra should overlay)
- MS-equipped: confirm molecular ion (m/z) and key fragment ions vs reference spectra
- Flag any peak not identifiable. Report as "unknown" with retention time and relative response
Got: All target analytes identified by retention time, with spectral confirmation where available. Unknown peaks flagged with retention time and area.
If fail: Retention times shifted uniformly? Systematic change happened (column aging, temperature drift, mobile phase error). Re-inject reference standard to establish current retention times before re-evaluating.
Step 3: Integrate Peaks
- Select integration mode:
- Automatic integration with data system defaults as starting point
- Manual adjust only when automatic demonstrably misplaces baseline or peak boundaries
- Set integration parameters:
- Baseline detection sensitivity (slope sensitivity / threshold)
- Minimum peak area or height to reject noise
- Peak width parameter matching narrowest expected peak
- Verify baseline placement:
- Baseline connects start and end of each peak at true chromatographic baseline
- Overlapping peaks: use valley-to-valley or perpendicular drop per method spec
- Gradient methods: baseline may rise — use tangent skim or exponential skim for peaks on rising baseline
- Check for integration errors:
- Split peaks integrated as two when they should be one
- Shoulder peaks merged into main peak when should be separate
- Noise spikes integrated as peaks
- Baseline drawn through peak (negative peak clipping)
- Record final integration parameters and any manual adjustments with justification in audit trail
Got: All target peaks integrated with correct baseline. No artifacts. All manual adjustments documented with rationale.
If fail: Automatic integrator consistently mishandles particular peak shape? Create timed-events integration method with custom parameters for that retention window. Never manually adjust integration to get desired result — adjustments must be scientifically justified.
Step 4: Calculate Chromatographic Parameters
Calculate for all reported peaks:
- Resolution (Rs) between adjacent peaks:
- Rs = 2(tR2 - tR1) / (w1 + w2)
- Rs >= 1.5 = baseline separation. Rs >= 2.0 = margin for routine use
- Tailing factor (T) at 5% peak height:
- T = W0.05 / (2f)
- T = 1.0 = perfectly symmetric. T > 2.0 = significant tailing
- Theoretical plates (N):
- N = 16(tR / w)^2 using baseline width, or N = 5.54(tR / w0.5)^2 using half-height width
- Higher N = better column efficiency
- Capacity factor (k'):
- k' = (tR - t0) / t0 where t0 = dead time (void volume / flow rate)
- Ideal range: 2-10 for good separation with reasonable run time
- Selectivity factor (alpha) between critical pair:
- alpha = k'2 / k'1
- alpha > 1.05 needed for adequate separation
- Tabulate results for all analytes. Compare vs method specs
Got: All chromatographic parameters calculated, tabulated, compared to acceptance criteria. Critical pair resolution and plate count documented.
If fail: Calculated plates much below column spec? Column maybe degraded — test with fresh standard, compare to historical data. Parameters drift within sequence? Investigate instrument stability.
Step 5: Assess Peak Quality
- Symmetry: Peaks should be Gaussian or near-Gaussian. Significant fronting (T < 0.8) = column overload. Tailing (T > 1.5) = secondary interactions or dead volume
- Baseline separation: Quant work — critical pairs must be baseline-resolved. Valley between peaks not returning to baseline? Note percentage valley, assess impact on accuracy
- Peak width consistency: Peaks much broader than expected (vs standard) → on-column degradation, extra-column band broadening, or injection issues
- Spectral purity (DAD/MS): Purity index shows spectral inhomogeneity across peak? Co-eluting impurity likely present. Adjust method for better resolution
- Negative peaks or baseline disturbances: Negative peaks in UV = sample solvent absorbs more than mobile phase at detection wavelength — normal for solvent front, abnormal elsewhere
- Ghost peaks: Peaks in blank injection = carryover, contaminated mobile phase, or column bleed. Identify source before reporting sample results
- Summarize overall chromatographic quality. Note any limitations on reported results
Got: Peak quality assessed for all target analytes. Any anomalies (tailing, co-elution, ghost peaks) documented with potential impact on data quality.
If fail: Significant quality issues found (co-elution confirmed by spectral impurity, ghost peaks at analyte retention times)? Data may not be reportable. Flag results, investigate root cause, re-run after corrective action.
Checks
- System suitability parameters calculated and within spec
- All target analytes identified by retention time (+/- spectral confirmation)
- Unknown peaks flagged with retention time and area
- Integration done with correct baseline. Manual adjustments documented
- Resolution, tailing, plates, capacity factor calculated for all peaks
- Peak quality assessed — no unresolved co-elutions affecting quantitation
- Ghost peaks and carryover evaluated via blank injection
- Results tabulated and compared vs method acceptance criteria
Pitfalls
- Accept automatic integration without review: Data systems misplace baselines, especially for shoulders, small peaks near large ones, gradient baselines. Every chromatogram needs visual review.
- Confuse retention time shift with new peak: Uniform shifts (all peaks move together) = systematic change, not new compounds. Re-inject standard to recalibrate before making ID calls.
- Report peaks below noise: Peaks with S/N below 3 (detection) or 10 (quantitation) should not be identified or quantitated. Calculate S/N explicitly for trace-level peaks.
- Ignore solvent front: Void volume peak not an analyte. Ensure t0 correctly identified and excluded from analyte reporting.
- Manual integration to hit target result: Adjusting integration to make result pass spec = data falsification. All integration changes must be scientifically justified, audit-trailed.
- Neglect spectral purity checks: Clean-looking peak can hide co-eluting impurity. Always check peak purity when DAD or MS data available.
See Also
develop-gc-method— method dev for GC technique making chromatogramdevelop-hplc-method— method dev for HPLC technique making chromatogramtroubleshoot-separation— diagnose problems found during chromatogram interpretationvalidate-analytical-method— formal validation of method generating chromatographic datainterpret-mass-spectrum— detailed interpretation of MS data for GC-MS and LC-MS peak confirmation
GitHub 저장소
연관 스킬
executing-plans
디자인executing-plans 스킬은 검토 체크포인트가 포함된 통제된 배치로 실행할 완전한 구현 계획이 있을 때 사용합니다. 이 스킬은 계획을 불러와 비판적으로 검토한 후, 소규모 배치(기본값 3개 작업)로 작업을 실행하면서 각 배치 사이에 진행 상황을 아키텍트 검토를 위해 보고합니다. 이를 통해 내재된 품질 관리 체크포인트를 갖춘 체계적인 구현이 보장됩니다.
requesting-code-review
디자인이 스킬은 코드 변경 사항을 요구 사항에 따라 분석하기 위해 코드 리뷰어 하위 에이전트를 호출합니다. 작업 완료 후, 주요 기능 구현 후, 또는 메인 브랜치에 병합하기 전에 사용해야 합니다. 이 리뷰는 현재 구현체와 원래 계획을 비교하여 문제를 조기에 발견하는 데 도움이 됩니다.
connect-mcp-server
디자인이 스킬은 개발자들이 HTTP, stdio 또는 SSE 전송 방식을 통해 MCP 서버를 Claude Code에 연결하는 포괄적인 가이드를 제공합니다. GitHub, Notion 및 사용자 정의 API와 같은 외부 서비스를 통합하기 위한 설치, 구성, 인증 및 보안을 다룹니다. MCP 통합 설정, 외부 도구 구성 또는 Claude의 모델 컨텍스트 프로토콜 작업 시 활용하세요.
web-cli-teleport
디자인이 스킬은 작업 분석을 기반으로 개발자가 Claude Code 웹 인터페이스와 CLI 인터페이스 중 선택할 수 있도록 돕고, 두 환경 간 원활한 세션 텔레포트를 가능하게 합니다. 웹, CLI 또는 모바일 환경 전환 시 세션 상태와 컨텍스트를 관리하여 워크플로를 최적화합니다. 다양한 단계에서 서로 다른 도구가 필요한 복잡한 프로젝트에 사용하세요.
