MCP HubMCP Hub
스킬 목록으로 돌아가기

interpret-chromatogram

pjt222
업데이트됨 Yesterday
1 조회
17
2
17
GitHub에서 보기
디자인design

정보

이 Claude Skill은 GC/HPLC 크로마토그램을 분석하여 시스템 적합성을 검증하고, 머무름 시간과 스펙트럼 매칭으로 피크를 식별하며, 품질 평가와 함께 적분을 수행합니다. 크로마토그래피 데이터를 처리하는 개발자들을 위해 신뢰할 수 있는 정량 분석을 보장하기 위해 성능 지표를 계산합니다. 데이터 검토, 방법 준수 확인, 또는 피크 적분 문제 해결 시에 사용하세요.

빠른 설치

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/interpret-chromatogram

Claude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요

문서

Interpret a Chromatogram

Systematic interpret GC/HPLC → system suitability, peak id, integration, param calc, peak quality → confident qual+quant.

Use When

  • Review chrom data before reporting
  • Verify system suitability passes before sample seq
  • ID unknown peaks / confirm analytes by tR / spectral
  • Troubleshoot peaks, baseline anomalies, integration artifacts
  • Train analysts → interpret

In

Req

  • Chromatogram: Digital/printed w/ time + detector axes
  • Ref standard: tR + response of known analytes (same method)
  • Method params: Column, mobile phase/carrier, temp/gradient, detector

Opt

  • Spectral: UV-Vis (DAD), MS, or other → peak confirm
  • Prior chroms: Historical data (same method) → trend
  • Suitability criteria: Method / regulatory limits
  • Prep details: Dilution, recovery, IS conc

Do

Step 1: Verify System Suitability

Confirm system in spec before interpret.

ParameterTypical SpecificationCalculation
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.2T = 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 analytek' = (tR - t0) / t0
  1. Locate suitability injections (usually 5-6 replicates ref std at seq start)
  2. Calc each param
  3. Compare vs acceptance criteria
  4. Any fail → system not suitable → don't proceed till fixed
  5. Doc results in batch record

→ All params in spec → system fit for purpose.

If err: tR RSD fails → check temp instability, mobile phase prep err, column degrade. Tailing fails → inspect inlet liner (GC) / column frit (HPLC). Res fails → test mix → replace column if needed.

Step 2: ID Peaks

  1. Compare peak tR vs ref std chrom
    • Acceptable: ±2% of ref tR (or ±0.1 min short runs)
  2. Ambiguous → co-injection (spike): add std to sample, re-inject. Target peak increases w/o broaden/shoulder.
  3. DAD HPLC: compare UV-Vis spectrum vs lib
    • Match index ≥ 990/1000 → positive ID
    • Check spectral purity across peak (front/apex/tail overlay)
  4. MS: confirm molecular ion (m/z) + key frag ions vs ref
  5. Flag unidentified → "unknown" w/ tR + rel response

→ All targets ID'd by tR match w/ spectral confirm where avail. Unknowns flagged w/ tR + area.

If err: tR uniformly shifted → systematic change (column age, temp drift, mobile phase err). Re-inject std → establish current tRs before re-eval.

Step 3: Integrate

  1. Select mode:
    • Auto w/ data sys defaults → start
    • Manual only when auto demonstrably misplaces baseline / peak boundary
  2. Set params:
    • Baseline sensitivity (slope / threshold)
    • Min area/height → reject noise
    • Peak width matches narrowest expected
  3. Verify baseline:
    • Connects start+end of peak at true baseline
    • Overlap → valley-to-valley / perpendicular drop per method
    • Gradient: rising baseline → tangent/exponential skim
  4. Check integration errs:
    • Split peaks as 2 when should be 1
    • Shoulder merged into main peak when should be sep
    • Noise spikes as peaks
    • Baseline thru peak (neg clip)
  5. Record final params + any manual + justification in audit trail

→ All targets integrated, correct baseline, no artifacts, manual docs w/ rationale.

If err: Auto consistently mishandles peak shape → timed-events integration w/ custom params for that window. Never adjust to achieve desired result → adjustments must be sci justified.

Step 4: Calc Chrom Params

Calc for all reported peaks:

  1. Resolution (Rs) adjacent:
    • Rs = 2(tR2 - tR1) / (w1 + w2)
    • Rs ≥ 1.5 → baseline sep; ≥ 2.0 → routine margin
  2. Tailing (T) at 5% height:
    • T = W0.05 / (2f)
    • 1.0 symmetric; >2.0 → significant tail
  3. Plates (N):
    • N = 16(tR / w)^2 baseline w, or N = 5.54(tR / w0.5)^2 half-h
    • Higher → better efficiency
  4. Capacity (k'):
    • k' = (tR - t0) / t0, t0 = dead time (void vol / flow)
    • Ideal 2-10 → good sep + reasonable run
  5. Selectivity (α) critical pair:
    • α = k'2 / k'1
    • α > 1.05 → adequate sep
  6. Tabulate all, compare vs method spec

→ All params calc, tabulated, compared vs criteria. Critical pair res + plate count documented.

If err: Plates below spec → column may be degraded → test fresh std, compare historical. Params drift in seq → investigate instrument stability.

Step 5: Assess Peak Quality

  1. Symmetry: Gaussian / near-Gaussian. Fronting (T < 0.8) → overload; tailing (T > 1.5) → secondary interactions / dead vol.
  2. Baseline sep: Quant → critical pairs must be baseline-resolved. Valley no return → note % valley + assess accuracy impact.
  3. Peak width consistency: Broader than expected (vs std) → on-column degradation, extra-column broadening, injection issues.
  4. Spectral purity (DAD/MS): Purity index → inhomogeneity → co-eluting impurity likely. Consider method adj for better res.
  5. Neg peaks / baseline disturb: Neg in UV → sample solvent absorbs more than mobile phase at λ → normal for solvent front, abnormal elsewhere.
  6. Ghost peaks: In blank → carryover, contaminated mobile phase, column bleed. ID source before report.
  7. Summarize quality + note limitations on reported results

→ Quality assessed per analyte. Anomalies (tail, co-elute, ghost) documented w/ data impact.

If err: Significant quality issues (co-elute confirmed by spectral impurity, ghost at analyte tR) → data may not be reportable. Flag, investigate root cause, re-run after corrective action.

Check

  • Suitability params calc + in spec
  • All targets ID'd by tR (± spectral)
  • Unknowns flagged w/ tR + area
  • Integration correct baseline, manual docs
  • Res, tail, plates, k' calc for all peaks
  • Quality assessed → no unresolved co-elute affecting quant
  • Ghost + carryover evaluated via blank
  • Results tabulated vs method acceptance

Traps

  • Accept auto integration w/o review: Data sys misplaces baselines, esp shoulders, small peaks near large, gradient baselines. Visual review always.
  • Confuse tR shift w/ new peak: Uniform tR shift (all move) → systematic change, not new compounds. Re-inject std → recalibrate before ID calls.
  • Report peaks below noise: S/N < 3 (detection) / < 10 (quant) → don't ID / quant. Calc S/N explicit for trace peaks.
  • Ignore solvent front: Void vol peak ≠ analyte. t0 correctly ID'd + excluded from reporting.
  • Manual integration → target result: Adjust to pass spec = data falsification. Changes must be sci justified + audit-trailed.
  • Neglect spectral purity: Clean peak can hide co-eluting impurity. Always check purity when DAD/MS avail.

  • develop-gc-method — method dev for GC producing chrom
  • develop-hplc-method — method dev for HPLC producing chrom
  • troubleshoot-separation — diagnose problems found during interpret
  • validate-analytical-method — formal validation of method generating data
  • interpret-mass-spectrum — detailed MS interpret for GC-MS / LC-MS peak confirm

GitHub 저장소

pjt222/agent-almanac
경로: i18n/caveman-ultra/skills/interpret-chromatogram
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

연관 스킬

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 또는 모바일 환경 전환 시 세션 상태와 컨텍스트를 관리하여 워크플로를 최적화합니다. 다양한 단계에서 서로 다른 도구가 필요한 복잡한 프로젝트에 사용하세요.

스킬 보기