Evidence Insight
uniprot-database
Direct REST API access to UniProt for protein search, entry retrieval, and identifier mapping; use when you need programmatic UniProtKB queries or cross-database ID conversion.
90100Total Score
Core Capability
87 / 100
Functional Suitability
11 / 12
Reliability
10 / 12
Performance & Context
8 / 8
Agent Usability
14 / 16
Human Usability
8 / 8
Security
9 / 12
Maintainability
10 / 12
Agent-Specific
17 / 20
Medical Task
20 / 20 Passed
97You need to search UniProtKB with Lucene-style queries (e.g., by gene name, organism, reviewed status)
4/4
93You want to fetch the full details of a specific protein entry by UniProt accession (e.g., P12345)
4/4
91Protein search via UniProtKB REST endpoint using Lucene query syntax
4/4
91Entry retrieval by accession with selectable output formats
4/4
91End-to-end case for Protein search via UniProtKB REST endpoint using Lucene query syntax
4/4
Veto GatesRequired pass for any deployment consideration
Skill Veto✓ All 4 gates passed
✓
Operational Stability
System remains stable across varied inputs and edge cases
PASS✓
Structural Consistency
Output structure conforms to expected skill contract format
PASS✓
Result Determinism
Equivalent inputs produce semantically equivalent outputs
PASS✓
System Security
No prompt injection, data leakage, or unsafe tool use detected
PASSResearch Veto✅ PASS — Applicable
| Dimension | Result | Detail |
|---|---|---|
| Scientific Integrity | PASS | The archived evaluation kept the skill tied to retrieved records or indexed source material rather than invented scientific claims. |
| Practice Boundaries | PASS | Practice boundaries held because the package remained focused on source handling, lookup, or structured evidence use. |
| Methodological Ground | PASS | No methodological-grounding issue was recorded for uniprot-database in the archived evaluation. |
| Code Usability | PASS | Code usability passed because the search or lookup workflow still exposed a usable entrypoint and output expectation. |
Core Capability87 / 100 — 8 Categories
Functional Suitability
Functional suitability was softened by the legacy issue 'Improve stress-case output rigor'. Stress and boundary scenarios show weaker consistency
11 / 12
92%
Reliability
The archived deduction in reliability traces back to: Improve stress-case output rigor. Stress and boundary scenarios show weaker consistency
10 / 12
83%
Performance & Context
No point loss was recorded for performance context in the legacy audit.
8 / 8
100%
Agent Usability
A modest deduction remained in agent usability for uniprot-database in the archived review.
14 / 16
88%
Human Usability
Human usability reached full score in the archived evaluation.
8 / 8
100%
Security
The archived evaluation left some headroom for uniprot-database under security.
9 / 12
75%
Maintainability
The legacy audit deducted points for uniprot-database in maintainability.
10 / 12
83%
Agent-Specific
Agent specific was softened by the legacy issue 'Improve stress-case output rigor'. Stress and boundary scenarios show weaker consistency
17 / 20
85%
Core Capability Total87 / 100
Medical TaskExecution Average: 92.6 / 100 — Assertions: 20/20 Passed
97
Canonical
You need to search UniProtKB with Lucene-style queries (e.g., by gene name, organism, reviewed status)
4/4 ✓
93
Variant A
You want to fetch the full details of a specific protein entry by UniProt accession (e.g., P12345)
4/4 ✓
91
Edge
Protein search via UniProtKB REST endpoint using Lucene query syntax
4/4 ✓
91
Variant B
Entry retrieval by accession with selectable output formats
4/4 ✓
91
Stress
End-to-end case for Protein search via UniProtKB REST endpoint using Lucene query syntax
4/4 ✓
97
Canonical✅ Pass
You need to search UniProtKB with Lucene-style queries (e.g., by gene name, organism, reviewed status)
The archived run for You need to search UniProtKB with Lucene-style queries (e.g., by... remained guidance-driven rather than command-driven.
Basic 36/40|Specialized 60/60|Total 97/100
✅A1The uniprot-database output structure matches the documented deliverable
✅A2The instruction path remains actionable for the documented case
✅A3The output stays fully within the documented skill boundary
✅A4The response quality is acceptable for the documented path
Pass rate: 4 / 4
93
Variant A✅ Pass
You want to fetch the full details of a specific protein entry by UniProt accession (e.g., P12345)
The archived run for You want to fetch the full details of a specific protein entry by... remained guidance-driven rather than command-driven.
Basic 34/40|Specialized 59/60|Total 93/100
✅A1The uniprot-database output structure matches the documented deliverable
✅A2The instruction path remains actionable for the documented case
✅A3The output stays fully within the documented skill boundary
✅A4The response quality is acceptable for the documented path
Pass rate: 4 / 4
91
Edge✅ Pass
Protein search via UniProtKB REST endpoint using Lucene query syntax
The archived run for Protein search via UniProtKB REST endpoint using Lucene query syntax remained guidance-driven rather than command-driven.
Basic 33/40|Specialized 58/60|Total 91/100
✅A1The uniprot-database output structure matches the documented deliverable
✅A2The instruction path remains actionable for the documented case
✅A3The output stays fully within the documented skill boundary
✅A4The response quality is acceptable for the documented path
Pass rate: 4 / 4
91
Variant B✅ Pass
Entry retrieval by accession with selectable output formats
Entry retrieval by accession with selectable output formats was evaluated as a bounded documentation path, not as a runnable script workflow.
Basic 32/40|Specialized 59/60|Total 91/100
✅A1The uniprot-database output structure matches the documented deliverable
✅A2The instruction path remains actionable for the documented case
✅A3The output stays fully within the documented skill boundary
✅A4The response quality is acceptable for the documented path
Pass rate: 4 / 4
91
Stress✅ Pass
End-to-end case for Protein search via UniProtKB REST endpoint using Lucene query syntax
This stress case stayed inside the documented workflow and remained instruction-led.
Basic 29/40|Specialized 60/60|Total 91/100
✅A1The uniprot-database output structure matches the documented deliverable
✅A2The instruction path remains actionable for the documented case
✅A3The output stays fully within the documented skill boundary
✅A4The response quality is acceptable for the documented path
Pass rate: 4 / 4
Medical Task Total92.6 / 100
Key Strengths
- Primary routing is Evidence Insight with execution mode B
- Static quality score is 87/100 and dynamic average is 79.6/100
- Assertions and command execution outcomes are recorded per input for human review
- Execution verification summary: Script verification 1/1; adjustment=5. uniprot_client.py: OK