Scienceofficial

human-protein-atlas-database

google-deepmind/science-skills · updated Jun 4, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/google-deepmind/science-skills --skill human-protein-atlas-database
0 commentsdiscussion
summary

### Human Protein Atlas Database

  • name: "human-protein-atlas-database"
  • description: "Use when you want to retrieve semi-quantitative protein expression and spatial localisation data from the Human Protein Atlas (HPA)."
skill.md
name
human-protein-atlas-database
description
> Use when you want to retrieve semi-quantitative protein expression and spatial localisation data from the Human Protein Atlas (HPA).

Human Protein Atlas (HPA) Database Integration

This skill provides semi-quantitative protein expression and spatial localisation data from the Human Protein Atlas (HPA). While RNA-seq (e.g., GTEx) tells us if a gene is being transcribed, HPA confirms if the protein product actually exists, where it is located within the cell (e.g. nucleus vs cytoplasm), and its concentration in systemic blood circulation. The data is based on Immunohistochemistry (IHC) across normal human tissues and cancer types.

Prerequisites

  1. uv: Read the uv skill and follow its Setup instructions to ensure uv is installed and on PATH.
  2. User Notification: If LICENSE_NOTIFICATION.txt does not already exist in this skill directory then (1) prominently notify the user to check the terms at https://www.proteinatlas.org/about/licence, then (2) create the file recording the notification text and timestamp.

When to Use

Use this skill when you need to:

  • Map a gene symbol to its Ensembl ID for HPA queries.
  • Retrieve the semi-quantitative protein abundance in normal human tissues and cancer types based on IHC staining (High, Medium, Low, or Not Detected).
  • Find the specific organelles or subcellular structures where a protein has been localized (e.g., nucleoplasm, mitochondria).
  • Check the consistency/agreement between RNA-seq consensus and protein expression levels.
  • Search for genes based on specific protein expression criteria (e.g., "elevated in amygdala" or "secreted proteins").

Do NOT use when you need to:

  • Query eQTLs, pQTLs, or any variant-level associations. HPA provides wild-type expression data and knows nothing about QTLs.
  • Query gene expression in non-human species. HPA is strictly for human proteins.
  • Retrieve purely quantitative RNA expression without interest in the protein product (consider using the GTEx skill instead).

Command Selection Guide

Pick the right command on the first try. Match the user's input to the correct subcommand below.

  • Map a gene symbol to Ensembl ID: resolve-ensembl-id
  • Get tissue protein expression levels: get-tissue-expression
  • Get subcellular location of a protein: get-subcellular-location
  • Get the full HPA metadata entry for a gene: get-atlas-entry
  • Search HPA for genes matching specific criteria: search-hpa

Quick Start

# Map the ERBB2 gene symbol to its Ensembl ID
uv run scripts/hpa_cli.py resolve-ensembl-id ERBB2 --output /tmp/erbb2_id.json

# Get subcellular location by Ensembl ID
uv run scripts/hpa_cli.py get-subcellular-location ENSG00000141736 --output /tmp/erbb2_location.json

All subcommands write JSON to disk. Always save output in the /tmp/ directory. The default output file is /tmp/hpa_output.json if --output is not specified.

Commands

1. resolve-ensembl-id — Gene Symbol → Ensembl ID

Maps a common gene symbol (e.g., "TP53", "ERBB2") to its Ensembl gene ID. HPA endpoints are strictly Ensembl-based.

uv run scripts/hpa_cli.py resolve-ensembl-id TP53 --output /tmp/tp53_id.json

Arguments:

  • gene_symbol (positional): The standard gene symbol (e.g., "TP53").
  • --output: Output file path (default: /tmp/hpa_output.json).

2. get-tissue-expression — Get Tissue Protein Levels

Returns a list of tissues and their corresponding protein expression levels (High, Medium, Low, or Not Detected) based on IHC staining.

uv run scripts/hpa_cli.py get-tissue-expression ENSG00000130234 \
  --tissues "duodenum,thyroid gland" --output /tmp/tissue_expr.json

Arguments:

  • ensembl_id (positional): The Ensembl Gene ID.
  • --tissues: Comma-separated list of tissues to filter by (optional, defaults to all available tissues).
  • --output: Output file path (default: /tmp/hpa_output.json).

3. get-subcellular-location — Get Subcellular Location

Retrieves the specific organelles or cellular structures where the protein has been localized.

uv run scripts/hpa_cli.py get-subcellular-location ENSG00000141736 \
  --output /tmp/subcellular.json

Arguments:

  • ensembl_id (positional): The Ensembl Gene ID.
  • --output: Output file path.

4. get-atlas-entry — Get Full HPA Entry

Fetches the full metadata for a gene, including IHC scores, RNA-seq consensus, and subcellular location.

uv run scripts/hpa_cli.py get-atlas-entry ENSG00000254647 \
  --output /tmp/ins_entry.json

Arguments:

  • ensembl_id (positional): The Ensembl Gene ID.
  • --format: Format of the returned entry, e.g., json (default: json).
  • --output: Output file path.

5. search-hpa — Search by Attribute

Allows filtering for genes based on specific criteria (e.g., "elevated in amygdala").

uv run scripts/hpa_cli.py search-hpa \
  --query "brain_category_rna:amygdala" \
  --output /tmp/search_results.json

Arguments:

  • --query: The search query string. Refer to references/search-api.md for details.
  • --output: Output file path.

Core Rules

  • Use the Wrapper: ALWAYS execute the provided helper scripts to query the database rather than accessing the database directly. The scripts automatically enforce fair use and implement retry logic.
  • Notification: If this skill is used, ensure this is mentioned in the output.

API Versioning

The HPA website at www.proteinatlas.org always serves the latest data release. Older archived versions can be accessed via vNN.proteinatlas.org (e.g., v24.proteinatlas.org), while the current version's subdomain redirects to www.proteinatlas.org. This skill's scripts query the latest version by default.

Common Errors

  • If no results are returned, confirm the query is detailed enough starting with the api reference in references/search-api.md
  • If you cannot find the results, search the web for example HPA queries and use these to construct a better query.
  • The output is usually large. Use jq or write your own python data parsing library to process the search results. Never output to stdout, or cat the output file.
how to use human-protein-atlas-database

How to use human-protein-atlas-database on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add human-protein-atlas-database
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/google-deepmind/science-skills --skill human-protein-atlas-database

The skills CLI fetches human-protein-atlas-database from GitHub repository google-deepmind/science-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/human-protein-atlas-database

Reload or restart Cursor to activate human-protein-atlas-database. Access the skill through slash commands (e.g., /human-protein-atlas-database) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.472 reviews
  • Fatima Singh· Dec 28, 2024

    human-protein-atlas-database has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Emma Reddy· Dec 28, 2024

    Keeps context tight: human-protein-atlas-database is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Nikhil Jain· Dec 24, 2024

    Registry listing for human-protein-atlas-database matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Olivia Srinivasan· Dec 24, 2024

    human-protein-atlas-database fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Emma Iyer· Dec 8, 2024

    Useful defaults in human-protein-atlas-database — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Arya Nasser· Dec 8, 2024

    Registry listing for human-protein-atlas-database matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Nikhil Khanna· Dec 4, 2024

    human-protein-atlas-database has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Charlotte Khanna· Nov 27, 2024

    We added human-protein-atlas-database from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Hiroshi Brown· Nov 27, 2024

    human-protein-atlas-database reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Fatima Zhang· Nov 19, 2024

    human-protein-atlas-database is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 72

1 / 8