domains / families / science / uniprot-database

uniprot-database

combined

Direct REST API access to UniProt. Protein searches, FASTA retrieval, ID mapping, Swiss-Prot/TrEMBL. For Python workflows with multiple databases, prefer bioservices (unified interface to 40+ services). Use this for direct HTTP/REST work or UniProt-specific control. Direct REST API access to UniProt for protein search, entry retrieval, and identifier mapping; use when you need programmatic UniProtKB queries or cross-database ID conversion.

When to use

• Searching for protein entries by name, gene symbol, accession, or organism
• Retrieving protein sequences in FASTA or other formats
• Mapping identifiers between UniProt and external databases (Ensembl, RefSeq, PDB, etc.)
• Accessing protein annotations including GO terms, domains, and functional descriptions
• Batch retrieving multiple protein entries efficiently
• Querying reviewed (Swiss-Prot) vs. unreviewed (TrEMBL) protein data
• Streaming large protein datasets
• Building custom queries with field-specific search syntax

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The copies overlap heavily on the UniProt REST endpoints, but they disagree on the recommended Python implementation and include material steps the others lack. The foryourhealth111, sickn33, and FreedomIntelligence copies are near-identical and point to a bundled scripts/uniprot_client.py helper, while the aipoch copy provides a self-contained inline Python client with explicit polling logic and dependency versions. Crowning one copy would hide the alternative implementation and the missing-script caveat present in the sickn33 copy.