uniprot-database▌
davila7/claude-code-templates · updated May 13, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
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.
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:
- Submit mapping job to:
https://rest.uniprot.org/idmapping/run - Check job status:
https://rest.uniprot.org/idmapping/status/{jobId} - 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 numberid- Entry namegene_names- Gene name(s)organism_name- Organismprotein_name- Protein namessequence- Amino acid sequencelength- Sequence lengthgo_*- Gene Ontology annotationscc_*- 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 queryget_protein(accession, format)- Retrieve single protein entrymap_ids(ids, from_db, to_db)- Map between identifier typesbatch_retrieve(accessions, format)- Retrieve multiple entriesstream_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
- Use reviewed entries when possible: Filter with
reviewed:truefor Swiss-Prot (manually curated) entries - Specify format explicitly: Choose the most appropriate format (FASTA for sequences, TSV for tabular data, JSON for programmatic parsing)
- Use field selection: Only request fields you need to reduce bandwidth and processing time
- Handle pagination: For large result sets, implement proper pagination or use the stream endpoint
- Cache results: Store frequently accessed data locally to minimize API calls
- Rate limiting: Be respectful of API resources; implement delays for large batch operations
- 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 queriesid_mapping_databases.md- Supported databases for ID mapping operationsquery_syntax.md- Comprehensive query syntax with advanced examplesapi_examples.md- Code examples in multiple languages (Python, curl, R)
Additional Resources
- API Documentation: https://www.uniprot.org/help/api
- Interactive API Explorer: https://www.uniprot.org/api-documentation
- REST Tutorial: https://www.uniprot.org/help/uniprot_rest_tutorial
- Query Syntax Help: https://www.uniprot.org/help/query-fields
- SPARQL Endpoint: https://sparql.uniprot.org/ (for advanced graph queries)
How to use uniprot-database on Cursor
AI-first code editor with Composer
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 uniprot-database
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches uniprot-database from GitHub repository davila7/claude-code-templates and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate uniprot-database. Access the skill through slash commands (e.g., /uniprot-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
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★33 reviews- ★★★★★Mia Shah· Dec 24, 2024
uniprot-database is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Mia Sharma· Nov 27, 2024
Keeps context tight: uniprot-database is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Mia Brown· Nov 15, 2024
Solid pick for teams standardizing on skills: uniprot-database is focused, and the summary matches what you get after install.
- ★★★★★Mia Johnson· Oct 18, 2024
uniprot-database is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Lucas Sanchez· Oct 6, 2024
uniprot-database has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Oshnikdeep· Sep 21, 2024
We added uniprot-database from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Dev Menon· Sep 17, 2024
Useful defaults in uniprot-database — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Meera Nasser· Sep 9, 2024
I recommend uniprot-database for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Piyush G· Sep 1, 2024
I recommend uniprot-database for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Maya Bhatia· Sep 1, 2024
We added uniprot-database from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 33