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.
90
86%
Does it follow best practices?
Impact
92%
1.04xAverage score across 6 eval scenarios
Passed
No known issues
Query syntax & field selection
Reviewed filter
100%
100%
Field-specific query syntax
100%
100%
Explicit format selection
100%
100%
Field selection parameter
100%
100%
Correct field name prefixes
100%
100%
Correct search endpoint URL
0%
0%
Boolean operators
100%
100%
Human organism filter
100%
100%
Provided script usage
100%
100%
Output written to file
100%
100%
ID mapping workflow
Submit job endpoint
100%
100%
Status polling endpoint
100%
100%
Results retrieval endpoint
100%
100%
Case-sensitive database names
100%
100%
Handles failedIds
60%
70%
Polling loop with wait
100%
100%
Provided script usage
100%
100%
Results saved to file
100%
100%
Input IDs from file
100%
100%
Summary stats output
100%
100%
Streaming & rate limiting
Stream endpoint used
100%
100%
Reviewed filter applied
100%
100%
Rate limiting implemented
80%
80%
Results cached locally
100%
100%
Streaming chunked processing
100%
100%
Explicit format selection
100%
100%
Provided script usage
100%
100%
TrEMBL quality note
100%
100%
Field selection used
100%
100%
Output file produced
100%
100%
Batch & individual sequence retrieval
Helper script used
100%
100%
FASTA format for sequences
100%
100%
batch_retrieve or OR-query used
0%
100%
Extended accession handled
100%
100%
Accession format recognition
0%
0%
Output FASTA written to file
100%
100%
Reviewed filter for search
0%
0%
Explicit format parameter
100%
100%
Single-entry retrieval endpoint
100%
50%
Retrieval count summary
100%
100%
Multi-database bioservices preference
bioservices package used
100%
70%
Multiple databases queried
100%
100%
No direct UniProt REST for primary workflow
100%
66%
Results joined across databases
100%
100%
Output written to file
100%
100%
Reviewed filter applied
100%
100%
Design choice documented
0%
70%
Field selection used
100%
100%
Rate limiting or delay
100%
100%
Pagination and advanced query syntax
Pagination loop implemented
100%
100%
Range query syntax
100%
100%
Wildcard in query
0%
100%
Boolean grouping with parentheses
0%
100%
Reviewed filter applied
100%
100%
Field selection specified
100%
100%
Helper script used
100%
100%
Organism filter applied
100%
100%
Total count reported
100%
100%
Results written to file
100%
100%
71add64
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.