agentleFS
geneontologygeneontology/go-skills/skills/uniprot-database/SKILL.md

uniprot-database

Skill1 starsChanged 31 days agoBSD-3-ClauseView on GitHub

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.

12 other projects use a version of this, 7 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use usfiscaldata, ena-database and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • yf8578Skill

    usfiscaldata

    Query the U.S. Treasury Fiscal Data API for federal financial data including national debt, government spending, revenue, interest rates, exchange rates, and savings bonds. Access 54 datasets and 182 data tables with no API key required. Use when working with U.S. federal fiscal data, national debt tracking (Debt to the Penny), Daily Treasury Statements, Monthly Treasury Statements, Treasury securities auctions, interest rates on Treasury securities, foreign exchange rates, savings bonds, or any U.S. government financial statistics.

    Also in 5 projects that use this

  • garri333Skill

    ena-database

    Access European Nucleotide Archive via API/FTP. Retrieve DNA/RNA sequences, raw reads (FASTQ), genome assemblies by accession, for genomics and bioinformatics pipelines. Supports multiple formats.

    Also in 5 projects that use this

  • garri333Skill

    gwas-database

    Query NHGRI-EBI GWAS Catalog for SNP-trait associations. Search variants by rs ID, disease/trait, gene, retrieve p-values and summary statistics, for genetic epidemiology and polygenic risk scores.

    Also in 5 projects that use this

  • +9 more from garri333

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search UniProt using natural language queries or structured search syntax.

    line 33
  2. Very specific:

    Use the API search endpoint: https://rest.uniprot.org/uniprotkb/search?query={query}&format={format}

    line 56
  3. Very specific:

    Check job status: https://rest.uniprot.org/idmapping/status/{jobId}

    line 78
  4. Distinctive:

    Use field selection: Only request fields you need to reduce bandwidth and processing time

    line 171

“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

UniProt Database

Overview

UniProt is the world's leading comprehensive protein sequence and functional information resource. Search proteins by name, gene, or accession, retrieve sequences in FASTA format, perform ID mapping across databases, access Swiss-Prot/TrEMBL annotations via REST API for protein analysis.

When to Use This Skill

This skill should be used when:

  • 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

Core Capabilities

1. Searching for Proteins

Search UniProt using natural language queries or structured search syntax.

Common search patterns:

# Search by protein name
query = "insulin AND organism_name:\"Homo sapiens\""

# Search by gene name
query = "gene:BRCA1 AND reviewed:true"

# Search by accession
query = "accession:P12345"

# Search by sequence length
query = "length:[100 TO 500]"

# Search by taxonomy
query = "taxonomy_id:9606"  # Human proteins

# Search by GO term
query = "go:0005515"  # Protein binding

Use the API search endpoint: https://rest.uniprot.org/uniprotkb/search?query={query}&format={format}

Supported formats: JSON, TSV, Excel, XML, FASTA, RDF, TXT

2. Retrieving Individual Protein Entries

Retrieve specific protein entries by accession number.

Accession number formats:

  • Classic: P12345, Q1AAA9, O15530 (6 characters: letter + 5 alphanumeric)
  • Extended: A0A022YWF9 (10 characters for newer entries)

Retrieve endpoint: https://rest.uniprot.org/uniprotkb/{accession}.{format}

Example: https://rest.uniprot.org/uniprotkb/P12345.fasta

3. Batch Retrieval and ID Mapping

Map protein identifiers between different database systems and retrieve multiple entries efficiently.

ID Mapping workflow:

  1. Submit mapping job to: https://rest.uniprot.org/idmapping/run
  2. Check job status: https://rest.uniprot.org/idmapping/status/{jobId}
  3. Retrieve results: https://rest.uniprot.org/idmapping/results/{jobId}

Supported databases for mapping:

  • UniProtKB AC/ID
  • Gene names
  • Ensembl, RefSeq, EMBL
  • PDB, AlphaFoldDB
  • KEGG, GO terms
  • And many more (see /references/id_mapping_databases.md)

Limitations:

  • Maximum 100,000 IDs per job
  • Results stored for 7 days

4. Streaming Large Result Sets

For large queries that exceed pagination limits, use the stream endpoint:

https://rest.uniprot.org/uniprotkb/stream?query={query}&format={format}

The stream endpoint returns all results without pagination, suitable for downloading complete datasets.

5. Customizing Retrieved Fields

Specify exactly which fields to retrieve for efficient data transfer.

Common fields:

  • accession - UniProt accession number
  • id - Entry name
  • gene_names - Gene name(s)
  • organism_name - Organism
  • protein_name - Protein names
  • sequence - Amino acid sequence
  • length - Sequence length
  • go_* - Gene Ontology annotations
  • cc_* - Comment fields (function, interaction, etc.)
  • ft_* - Feature annotations (domains, sites, etc.)

Example: https://rest.uniprot.org/uniprotkb/search?query=insulin&fields=accession,gene_names,organism_name,length,sequence&format=tsv

See /references/api_fields.md for complete field list.

Python Implementation

For programmatic access, use the provided helper script scripts/uniprot_client.py which implements:

  • search_proteins(query, format) - Search UniProt with any query
  • get_protein(accession, format) - Retrieve single protein entry
  • map_ids(ids, from_db, to_db) - Map between identifier types
  • batch_retrieve(accessions, format) - Retrieve multiple entries
  • stream_results(query, format) - Stream large result sets

Alternative Python packages:

  • Unipressed: Modern, typed Python client for UniProt REST API
  • bioservices: Comprehensive bioinformatics web services client

Query Syntax Examples

Boolean operators:

kinase AND organism_name:human
(diabetes OR insulin) AND reviewed:true
cancer NOT lung

Field-specific searches:

gene:BRCA1
accession:P12345
organism_id:9606
taxonomy_name:"Homo sapiens"
annotation:(type:signal)

Range queries:

length:[100 TO 500]
mass:[50000 TO 100000]

Wildcards:

gene:BRCA*
protein_name:kinase*

See /references/query_syntax.md for comprehensive syntax documentation.

Best Practices

  1. Use reviewed entries when possible: Filter with reviewed:true for Swiss-Prot (manually curated) entries
  2. Specify format explicitly: Choose the most appropriate format (FASTA for sequences, TSV for tabular data, JSON for programmatic parsing)
  3. Use field selection: Only request fields you need to reduce bandwidth and processing time
  4. Handle pagination: For large result sets, implement proper pagination or use the stream endpoint
  5. Cache results: Store frequently accessed data locally to minimize API calls
  6. Rate limiting: Be respectful of API resources; implement delays for large batch operations
  7. Check data quality: TrEMBL entries are computational predictions; Swiss-Prot entries are manually reviewed

Resources

scripts/

uniprot_client.py - Python client with helper functions for common UniProt operations including search, retrieval, ID mapping, and streaming.

references/

  • api_fields.md - Complete list of available fields for customizing queries
  • id_mapping_databases.md - Supported databases for ID mapping operations
  • query_syntax.md - Comprehensive query syntax with advanced examples
  • api_examples.md - Code examples in multiple languages (Python, curl, R)

Additional Resources

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.