hmdb-database
Access Human Metabolome Database (220K+ metabolites). Search by name/ID/structure, retrieve chemical properties, biomarker data, NMR/MS spectra, pathways, for metabolomics and identification.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 3.3w
- Forks
- 3.9k
01 前言 Front Matter
- name
- hmdb-database
- description
- Access Human Metabolome Database (220K+ metabolites). Search by name/ID/structure, retrieve chemical properties, biomarker data, NMR/MS spectra, pathways, for metabolomics and identification.
02 资源文件 1
- 参考文档references/hmdb_data_fields.md8.5 KB
03 SKILL.md 正文
HMDB Database
Overview
The Human Metabolome Database (HMDB) is a comprehensive, freely available resource containing detailed information about small molecule metabolites found in the human body.
When to Use This Skill
This skill should be used when performing metabolomics research, clinical chemistry, biomarker discovery, or metabolite identification tasks.
Database Contents
HMDB version 5.0 (current as of 2025) contains:
- 220,945 metabolite entries covering both water-soluble and lipid-soluble compounds
- 8,610 protein sequences for enzymes and transporters involved in metabolism
- 130+ data fields per metabolite including:
- Chemical properties (structure, formula, molecular weight, InChI, SMILES)
- Clinical data (biomarker associations, diseases, normal/abnormal concentrations)
- Biological information (pathways, reactions, locations)
- Spectroscopic data (NMR, MS, MS-MS spectra)
- External database links (KEGG, PubChem, MetaCyc, ChEBI, PDB, UniProt, GenBank)
Core Capabilities
1. Web-Based Metabolite Searches
Access HMDB through the web interface at https://www.hmdb.ca/ for:
Text Searches:
- Search by metabolite name, synonym, or identifier (HMDB ID)
- Example HMDB IDs: HMDB0000001, HMDB0001234
- Search by disease associations or pathway involvement
- Query by biological specimen type (urine, serum, CSF, saliva, feces, sweat)
Structure-Based Searches:
- Use ChemQuery for structure and substructure searches
- Search by molecular weight or molecular weight range
- Use SMILES or InChI strings to find compounds
Spectral Searches:
- LC-MS spectral matching
- GC-MS spectral matching
- NMR spectral searches for metabolite identification
Advanced Searches:
- Combine multiple criteria (name, properties, concentration ranges)
- Filter by biological locations or specimen types
- Search by protein/enzyme associations
2. Accessing Metabolite Information
When retrieving metabolite data, HMDB provides:
Chemical Information:
- Systematic name, traditional names, and synonyms
- Chemical formula and molecular weight
- Structure representations (2D/3D, SMILES, InChI, MOL file)
- Chemical taxonomy and classification
Biological Context:
- Metabolic pathways and reactions
- Associated enzymes and transporters
- Subcellular locations
- Biological roles and functions
Clinical Relevance:
- Normal concentration ranges in biological fluids
- Biomarker associations with diseases
- Clinical significance
- Toxicity information when applicable
Analytical Data:
- Experimental and predicted NMR spectra
- MS and MS-MS spectra
- Retention times and chromatographic data
- Reference peaks for identification
3. Downloadable Datasets
HMDB offers bulk data downloads at https://www.hmdb.ca/downloads in multiple formats:
Available Formats:
- XML: Complete metabolite, protein, and spectra data
- SDF: Metabolite structure files for cheminformatics
- FASTA: Protein and gene sequences
- TXT: Raw spectra peak lists
- CSV/TSV: Tabular data exports
Dataset Categories:
- All metabolites or filtered by specimen type
- Protein/enzyme sequences
- Experimental and predicted spectra (NMR, GC-MS, MS-MS)
- Pathway information
Best Practices:
- Download XML format for comprehensive data including all fields
- Use SDF format for structure-based analysis and cheminformatics workflows
- Parse CSV/TSV formats for integration with data analysis pipelines
- Check version dates to ensure up-to-date data (current: v5.0, 2023-07-01)
Usage Requirements:
- Free for academic and non-commercial research
- Commercial use requires explicit permission (contact samackay@ualberta.ca)
- Cite HMDB publication when using data
4. Programmatic API Access
API Availability: HMDB does not provide a public REST API. Programmatic access requires contacting the development team:
- Academic/Research groups: Contact eponine@ualberta.ca (Eponine) or samackay@ualberta.ca (Scott)
- Commercial organizations: Contact samackay@ualberta.ca (Scott) for customized API access
Alternative Programmatic Access:
- R/Bioconductor: Use the
hmdbQuerypackage for R-based queries- Install:
BiocManager::install("hmdbQuery") - Provides HTTP-based querying functions
- Install:
- Downloaded datasets: Parse XML or CSV files locally for programmatic analysis
- Web scraping: Not recommended; contact team for proper API access instead
5. Common Research Workflows
Metabolite Identification in Untargeted Metabolomics:
- Obtain experimental MS or NMR spectra from samples
- Use HMDB spectral search tools to match against reference spectra
- Verify candidates by checking molecular weight, retention time, and MS-MS fragmentation
- Review biological plausibility (expected in specimen type, known pathways)
Biomarker Discovery:
- Search HMDB for metabolites associated with disease of interest
- Review concentration ranges in normal vs. disease states
- Identify metabolites with strong differential abundance
- Examine pathway context and biological mechanisms
- Cross-reference with literature via PubMed links
Pathway Analysis:
- Identify metabolites of interest from experimental data
- Look up HMDB entries for each metabolite
- Extract pathway associations and enzymatic reactions
- Use linked SMPDB (Small Molecule Pathway Database) for pathway diagrams
- Identify pathway enrichment for biological interpretation
Database Integration:
- Download HMDB data in XML or CSV format
- Parse and extract relevant fields for local database
- Link with external IDs (KEGG, PubChem, ChEBI) for cross-database queries
- Build local tools or pipelines incorporating HMDB reference data
Related HMDB Resources
The HMDB ecosystem includes related databases:
- DrugBank: ~2,832 drug compounds with pharmaceutical information
- T3DB (Toxin and Toxin Target Database): ~3,670 toxic compounds
- SMPDB (Small Molecule Pathway Database): Pathway diagrams and maps
- FooDB: ~70,000 food component compounds
These databases share similar structure and identifiers, enabling integrated queries across human metabolome, drug, toxin, and food databases.
Best Practices
Data Quality:
- Verify metabolite identifications with multiple evidence types (spectra, structure, properties)
- Check experimental vs. predicted data quality indicators
- Review citations and evidence for biomarker associations
Version Tracking:
- Note HMDB version used in research (current: v5.0)
- Databases are updated periodically with new entries and corrections
- Re-query for updates when publishing to ensure current information
Citation:
- Always cite HMDB in publications using the database
- Reference specific HMDB IDs when discussing metabolites
- Acknowledge data sources for downloaded datasets
Performance:
- For large-scale analysis, download complete datasets rather than repeated web queries
- Use appropriate file formats (XML for comprehensive data, CSV for tabular analysis)
- Consider local caching of frequently accessed metabolite information
Reference Documentation
See references/hmdb_data_fields.md for detailed information about available data fields and their meanings.
04 同仓库更多 Skills
wealthville-pool-scoring
Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter/Hold/Exit/Reduce/Avoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.
technical-debt-auditor
Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO/FIXME/HACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like "where should I focus refactoring", "find code smells", "audit my codebase", "what technical debt do we have", "prioritize cleanup work", or asks about code quality metrics. Also trigger when the user mentions "code rot", "legacy cleanup", "refactoring priorities", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say "technical debt" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.
readonly-sql-guard
Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production/ERP/analytics database (a "query" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write/DDL/side-effect/transaction-escape risks. Checks what a statement CALLS, not just its shape.
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
discernment-nudge
After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.