Generated banner for Uniprot Database
Generated logo for Uniprot Database

Uniprot Database

Google DeepMindOfficialPublished by Google DeepMind

  • Skill
  • Tool integration
  • Science and research
  • Apache-2.0
  • Low risk
  • Has scripts

From the author

Access protein metadata, function, taxonomy, and sequences across UniProtKB, UniParc, and UniRef. Use when searching for proteins, mapping identifiers, or retrieving functional annotations and publications. Don't use for sequence alignment, protein folding, or sequence similarity search (use specialized skills for those tasks).
— the description by Google DeepMind

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The UniProt Database skill provides a robust interface for interacting with the UniProt Knowledgebase (UniProtKB), UniParc, and UniRef. It enables researchers and developers to perform protein discovery, retrieve curated biological annotations, map identifiers across numerous external databases, and conduct bulk data retrieval. The skill is designed for programmatic access, ensuring reliable data extraction for bioinformatics workflows while adhering to UniProt's licensing and usage guidelines.

What it does

  • Retrieves detailed protein metadata, functional annotations, and sequences.
  • Maps protein identifiers between UniProt and over 100 external biological databases.
  • Performs complex queries and data discovery using SPARQL.
  • Supports bulk data retrieval through streaming for large datasets.
  • Provides access to historical data entries via UniSave.
  • Enables exploration of protein-organism relationships and taxonomy.

When to use it

  • When you need to fetch specific protein information by accession number.
  • When performing large-scale analysis requiring bulk retrieval of protein data.
  • When you need to convert identifiers from external databases to UniProt accessions.
  • When searching for proteins based on specific functional, gene, or taxonomic criteria.
  • When investigating historical versions of protein entries.

Advantages

  • Direct programmatic access to authoritative biological data.
  • Efficient handling of both single-entry lookups and large-scale data streams.
  • Powerful filtering capabilities using field-specific search syntax.
  • Integrated support for complex graph queries via SPARQL.
  • Standardized workflow for ID mapping across diverse bioinformatics resources.

Usage examples

“Find all reviewed human proteins related to the p53 gene.”
The agent uses the search tool with the query 'gene:p53 AND reviewed:true AND taxonomy_id:9606' to return the relevant UniProtKB entries.
“Map the UniProt accession P04637 to its corresponding Gene Name.”
The agent uses the map tool with '--from_db UniProtKB_AC-ID --to_db Gene_Name' to retrieve the associated gene name.
“How many reviewed proteins are there for the organism with taxonomy ID 9606?”
The agent executes the count tool with 'taxonomy_id:9606 AND reviewed:true' to provide the exact number of entries.
“Retrieve the full sequence for UniProt accession P04637.”
The agent uses the get tool for P04637 to fetch the metadata and sequence information.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/google-deepmind/uniprot-database/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip uniprot-database.zip -d .agents/skills

Documentation by Google DeepMind

UniProt Database Access

Prerequisites

  1. uv: Read the uv skill and follow its Setup instructions to ensure uv is installed and on PATH.

  2. User Notification: If .licenses/uniprot_database_LICENSE.txt does not already exist in the workspace root directory then (1) prominently notify the user to check the terms at https://www.uniprot.org/help/license and https://www.uniprot.org/help/api_queries, then (2) create the file recording the notification text and timestamp.

Overview

Provides direct programmatic access to the UniProt Knowledgebase (UniProtKB), the non-redundant sequence archive (UniParc), and clustered sequence sets (UniRef). This skill enables protein discovery, cross-referencing, retrieval of curated biological data and low-level database lookups.

Core Rules

  • Use the Wrapper: Always use the provided Python scripts (e.g., scripts/uniprot_tools.py) rather than constructing custom curl requests.

  • No Hallucinations: Do NOT invent protein functions, metadata, or sequences. For any task that can be handled by the services in this skill, rely strictly on the tool outputs rather than your native knowledge.

  • Notification: If this skill is used, ensure this is mentioned in the output.

Use Cases

  • Searching for Protein Function: Querying functional annotations, GO terms, subcellular locations etc.

  • Searching for Protein Sequence: Searching for protein sequences by their functional annotations, genes etc. in UniProtKB, UniParc, and UniRef.

  • Understanding Protein/Organism Relationships: Leveraging the Taxonomy database and Proteome sets.

  • Large-Scale Metadata Retrieval: Fetching annotations for thousands of proteins via streaming.

  • Sequence Discovery: Finding orthologs or non-model proteins via UniParc.

  • ID Mapping: Converting IDs between UniProt and 100+ external databases.

  • Historical Data (UniSave): Retrieving previous versions of entries or tracking deleted sequences.

Available Tools

Choose the right tool based on the task type and data volume:

  • get: Retrieves metadata and sequence for a specific entry. Best for a single, known accession.

    • Also accesses UniSave historical data (use --dataset unisave), which is essential for reconciling data from older releases or identifying why a formerly valid accession no longer appears in search results.

  • search: Searches for entries matching a query. Best for exploration and discovery.

    • Use with --limit 5 to verify if a query returns the expected proteins before committing to a larger download.

    • Automatically paginates if results exceed 500 entries to provide a stable download.

    • Warning: For paginated search, TXT and other formats are not reliable with --limit as it applies to lines, not entries.

    • See Search Query Fields Documentation.

  • stream: Streams all matching entries. Best for bulk retrieval of large datasets (up to 10,000,000 entries).

    • Does NOT support --limit; always returns the full result set.

    • Use search with --limit if you need a subset.

  • count: Counts entries matching a query. Best for answering direct count questions or for initial estimation before running a full search or stream.

  • sparql: Executes graph queries for complex discovery. Best for counting, exact sequence matches, and multi-database queries.

  • map: Converts IDs between UniProt and 100+ databases. Best for ID mapping tasks.

    • See ID Mapping Documentation.

    • search vs. map: Try search first before resorting to map if not explicitly requested by the user. E.g., an external ID might be searchable in UniParc but fail to map to UniProtKB.

Workflows

Typical Protein Research Workflow

Copy this checklist and track progress:

  • [ ] Step 1: Identify target protein(s) and organism(s).

  • [ ] Step 2: Search UniProtKB for reviewed entries (reviewed:true).

  • [ ] Step 3: If no reviewed entries, search unreviewed or use UniParc for sequence discovery.

  • [ ] Step 4: Map external IDs (e.g., Ensembl, PDB) to UniProt Accessions if necessary.

  • [ ] Step 5: Retrieve functional metadata or sequence in desired format (JSON, FASTA).

Handling Search Misses (e.g. Gene Search in Non-Model Organisms)

If a direct query (e.g., gene:SYMBOL) fails:

  1. Pivot to Protein Name: Search for the common protein name (e.g., protein_name:Alpha-crystallin A).

  2. Use UniParc: Search the UniParc dataset, which integrates sequences from across all of life, even if they aren't fully annotated in UniProtKB.

  3. Check Orthologs/Canonical: Resolve the Human/Mouse ortholog first to find the correct naming/mnemonic.

Bulk Retrieval Priorities

[!IMPORTANT] Always prefer stream or sparql for bulk data. search is suitable for exploration; if results exceed 500 entries, it automatically paginates to provide a stable download.

  • Priority 0: count: ALWAYS check the result count before running a search or stream.

  • Priority 1: stream: The primary method for bulk data retrieval (up to 10M entries). Does NOT support --limit; always returns all results.

  • Priority 2: sparql: Best for complex filtering and exact matching during retrieval.

Sequence-Based Search (Exact Match)

[!IMPORTANT] Use SPARQL when searching for a protein by its full amino acid sequence. The REST API /search endpoint does not support direct sequence-string lookups. For any non-exact match use specialized sequence similarity search skills. Use UniParc if you cannot find query in UniProt.

SPARQL Query Pattern (UniProt):

PREFIX up: <http://purl.uniprot.org/core/>
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
SELECT ?protein ?name WHERE {
  ?protein a up:Protein ;
           up:sequence/rdf:value "SEQUENCE_HERE" .
  OPTIONAL {
    ?protein up:recommendedName/up:fullName ?name .
  }
}

SPARQL Query Pattern (UniParc):

PREFIX up: <http://purl.uniprot.org/core/>
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>

SELECT ?uniparc ?val WHERE {
  GRAPH <http://sparql.uniprot.org/uniparc> {
    ?uniparc a up:Sequence ;
             rdf:value ?val .
    FILTER (?val = "SEQUENCE_HERE")
  }
}
Counting Entries Efficiently

[!IMPORTANT] Use count or SPARQL for counting entries (e.g., "How many proteins in Human?").

Counting Pattern (Proteins per Organism):

PREFIX up: <http://purl.uniprot.org/core/>
PREFIX taxon: <http://purl.uniprot.org/taxonomy/>
SELECT (COUNT(?protein) AS ?count) WHERE {
  ?protein a up:Protein ;
           up:reviewed true ;
           up:organism taxon:9606 .
}
REST Search Syntax
  • No Commas in Lists: Commas are treated as literals. Use capitalized OR to separate items.

    • Grouped: accession:(P12345 OR P67890)

    • Repeated: accession:P12345 OR accession:P67890

  • Space = AND: E.g., gene:p53 human searches for both.

Example Commands

Below are example commands for each mode of uniprot_tools.py.

Count total number of entries for a given query.

uv run scripts/uniprot_tools.py count "taxonomy_id:9606"

Search for entries.

uv run scripts/uniprot_tools.py search "gene:p53 AND reviewed:true" --limit 5

Retrieve a single entry by accession.

uv run scripts/uniprot_tools.py get P04637

Retrieve Historical/Deleted Entry (UniSave).

uv run scripts/uniprot_tools.py get P04637 --dataset unisave

Stream large result sets for bulk retrieval (returns ALL matched entries, no --limit support).

uv run scripts/uniprot_tools.py stream "taxonomy_id:9606 AND reviewed:true" --format tsv --fields accession,gene_names > human_reviewed.tsv

Map IDs from one database to another.

uv run scripts/uniprot_tools.py map "P04637" --from_db UniProtKB_AC-ID --to_db Gene_Name

Execute graph queries with SPARQL.

uv run scripts/uniprot_tools.py sparql 'PREFIX up: <http://purl.uniprot.org/core/> SELECT ?protein WHERE { ?protein a up:Protein ; up:reviewed true . } LIMIT 5'

Common Mistakes

  • Using name: instead of protein_name:: name: is not a supported query term, use protein_name: instead.

  • Ignoring UniParc: Non-model organisms might only exist in UniParc.

  • Confusing Accession with UPI: UniProtKB Accessions (e.g., P04637) are linked to functional metadata; UniParc IDs (UPI...) are for sequences only. You can find cross-references from UniParc IDs to UniProtKB Accessions using the ID Mapping tool.

  • Using UniProtKB-AC as Target in ID Mapping: Use UniProtKB instead.

  • Giving up on Complex Queries: If a complex search query fails, try to use SPARQL instead of giving up.

  • Using IDs Without Verifying Meaning: NEVER assume you know the meaning of an ID (e.g. keyword, GO term, Pfam ID etc.). ALWAYS look up the natural language description/meaning of an ID in UniProt before using it for search to ensure it matches your intended search term.

  • Ignoring Citation Noise in Broad Searches: Broad text searches (search "term") frequently return false positives (e.g., common maintenance proteins) because UniProt searches full metadata, including publication titles. ALWAYS prefer field-specific filters like cc_function: or protein_name: for functional discovery.

  • Forgetting to Quote Short Search Terms: Short, unquoted terms (e.g., lanM) can match substrings in organism names (e.g., Lancefieldella) or other fields. Use quotes and field prefixes (e.g., gene:lanM) to isolate true hits.

  • Manipulating Protein Sequences Directly: Always use code and tools for sequence-based operations. Do not attempt to edit, truncate, or modify protein sequences manually.

  • Over-using Search for Bulk Data: DO NOT use search for retrieving millions of entries if stream or sparql can do the job. Streaming is more efficient for very large datasets. Note that stream has a hard limit of 10,000,000 outputs and does NOT support --limit.

  • Forgetting to Check Data Volume: ALWAYS perform a count before running a search without --limit or before using stream. Unlimited queries can take a long time and consume significant resources if millions of entries are returned.

  • Using --limit with stream: The stream command does NOT support --limit. If you need a limited number of results, use search with --limit instead.

  • Forgetting the License Notice: Do not neglect to state that the UniProt Database was used and to advise the user to review the licensing terms when presenting results for the first time. Even if the task is concise, this attribution is required in the first response containing UniProt data.

Reference Materials

Files

LICENSE


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs Python

Security

What our scanner noticed· Low risk

  • Scripts that your agent may run

This skill includes scripts that your agent may run. Read them before you use it.

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Google DeepMind
Publisher
Google DeepMind (Official)
Source
google-deepmind/science-skills · skills/uniprot_database · commit 4de6786
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Google DeepMind.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download uniprot-database.zip