interpret-chromatogram
À propos
Cette Compétence Claude analyse les chromatogrammes GC/HPLC pour vérifier l'aptitude du système, identifier les pics par temps de rétention et correspondance spectrale, et réaliser l'intégration avec évaluation de la qualité. Elle calcule les figures de mérite pour garantir une quantification fiable aux développeurs traitant des données chromatographiques. Utilisez-la lors de l'examen des données, de la confirmation de la conformité de la méthode ou du dépannage des problèmes d'intégration des pics.
Installation rapide
Claude Code
Recommandé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-chromatogramCopiez et collez cette commande dans Claude Code pour installer cette compétence
Documentation
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.
| 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 suitability injections (usually 5-6 replicates ref std at seq start)
- Calc each param
- Compare vs acceptance criteria
- Any fail → system not suitable → don't proceed till fixed
- 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
- Compare peak tR vs ref std chrom
- Acceptable: ±2% of ref tR (or ±0.1 min short runs)
- Ambiguous → co-injection (spike): add std to sample, re-inject. Target peak increases w/o broaden/shoulder.
- DAD HPLC: compare UV-Vis spectrum vs lib
- Match index ≥ 990/1000 → positive ID
- Check spectral purity across peak (front/apex/tail overlay)
- MS: confirm molecular ion (m/z) + key frag ions vs ref
- 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
- Select mode:
- Auto w/ data sys defaults → start
- Manual only when auto demonstrably misplaces baseline / peak boundary
- Set params:
- Baseline sensitivity (slope / threshold)
- Min area/height → reject noise
- Peak width matches narrowest expected
- Verify baseline:
- Connects start+end of peak at true baseline
- Overlap → valley-to-valley / perpendicular drop per method
- Gradient: rising baseline → tangent/exponential skim
- 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)
- 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:
- Resolution (Rs) adjacent:
- Rs = 2(tR2 - tR1) / (w1 + w2)
- Rs ≥ 1.5 → baseline sep; ≥ 2.0 → routine margin
- Tailing (T) at 5% height:
- T = W0.05 / (2f)
- 1.0 symmetric; >2.0 → significant tail
- Plates (N):
- N = 16(tR / w)^2 baseline w, or N = 5.54(tR / w0.5)^2 half-h
- Higher → better efficiency
- Capacity (k'):
- k' = (tR - t0) / t0, t0 = dead time (void vol / flow)
- Ideal 2-10 → good sep + reasonable run
- Selectivity (α) critical pair:
- α = k'2 / k'1
- α > 1.05 → adequate sep
- 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
- Symmetry: Gaussian / near-Gaussian. Fronting (T < 0.8) → overload; tailing (T > 1.5) → secondary interactions / dead vol.
- Baseline sep: Quant → critical pairs must be baseline-resolved. Valley no return → note % valley + assess accuracy impact.
- Peak width consistency: Broader than expected (vs std) → on-column degradation, extra-column broadening, injection issues.
- Spectral purity (DAD/MS): Purity index → inhomogeneity → co-eluting impurity likely. Consider method adj for better res.
- Neg peaks / baseline disturb: Neg in UV → sample solvent absorbs more than mobile phase at λ → normal for solvent front, abnormal elsewhere.
- Ghost peaks: In blank → carryover, contaminated mobile phase, column bleed. ID source before report.
- 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 chromdevelop-hplc-method— method dev for HPLC producing chromtroubleshoot-separation— diagnose problems found during interpretvalidate-analytical-method— formal validation of method generating datainterpret-mass-spectrum— detailed MS interpret for GC-MS / LC-MS peak confirm
Dépôt GitHub
Compétences associées
executing-plans
DesignUtilisez la compétence executing-plans lorsque vous disposez d'un plan de mise en œuvre complet à exécuter par lots contrôlés avec des points de contrôle de revue. Elle charge et examine le plan de manière critique, puis exécute les tâches par petits lots (3 tâches par défaut) tout en rapportant la progression entre chaque lot pour une revue par l'architecte. Cela garantit une mise en œuvre systématique avec des points de contrôle de qualité intégrés.
requesting-code-review
DesignCette compétence délègue un sous-agent réviseur de code pour analyser les modifications apportées au code par rapport aux exigences avant de poursuivre. Elle doit être utilisée après avoir terminé des tâches, implémenté des fonctionnalités majeures, ou avant une fusion vers la branche principale. La revue aide à détecter précocement les problèmes en comparant l'implémentation actuelle avec le plan initial.
connect-mcp-server
DesignCette compétence fournit un guide complet permettant aux développeurs de connecter des serveurs MCP à Claude Code via les transports HTTP, stdio ou SSE. Elle couvre l'installation, la configuration, l'authentification et la sécurité pour intégrer des services externes tels que GitHub, Notion et des API personnalisées. Utilisez-la lors de la configuration d'intégrations MCP, de la configuration d'outils externes ou du travail avec le Protocole de Contexte de Modèle de Claude.
web-cli-teleport
DesignCette compétence aide les développeurs à choisir entre les interfaces Web et CLI de Claude Code en fonction de l'analyse des tâches, puis permet une téléportation transparente des sessions entre ces environnements. Elle optimise le flux de travail en gérant l'état et le contexte de la session lors du passage entre le web, la CLI ou le mobile. Utilisez-la pour des projets complexes nécessitant différents outils à diverses étapes.
