Evidence Insight
drugbank-database
89100Total 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
95You need to extract structured drug properties (e.g., identifiers, synonyms, ATC codes) from DrugBank XML for downstream analysis
4/4
91You want to build and analyze drug–drug interaction (DDI) networks from DrugBank interaction records
4/4
89Programmatic download of DrugBank releases via drugbank-downloader (requires DrugBank access)
4/4
89XML parsing and traversal using lxml for reliable extraction of nested DrugBank entities
4/4
89End-to-end case for Programmatic download of DrugBank releases via drugbank-downloader (requires DrugBank access)
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 legacy audit did not indicate that retrieval outputs were presented as unsupported findings. |
| Practice Boundaries | PASS | Practice boundaries held because the package remained focused on source handling, lookup, or structured evidence use. |
| Methodological Ground | PASS | The older review treated the package logic as methodologically aligned with its stated workflow. |
| 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
The legacy audit gave full marks to performance context for this package.
8 / 8
100%
Agent Usability
A modest deduction remained in agent usability for drugbank-database in the archived review.
14 / 16
88%
Human Usability
No point loss was recorded for human usability in the legacy audit.
8 / 8
100%
Security
The archived evaluation left some headroom for drugbank-database under security.
9 / 12
75%
Maintainability
A modest deduction remained in maintainability for drugbank-database in the archived review.
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: 90.6 / 100 — Assertions: 20/20 Passed
95
Canonical
You need to extract structured drug properties (e.g., identifiers, synonyms, ATC codes) from DrugBank XML for downstream analysis
4/4 ✓
91
Variant A
You want to build and analyze drug–drug interaction (DDI) networks from DrugBank interaction records
4/4 ✓
89
Edge
Programmatic download of DrugBank releases via drugbank-downloader (requires DrugBank access)
4/4 ✓
89
Variant B
XML parsing and traversal using lxml for reliable extraction of nested DrugBank entities
4/4 ✓
89
Stress
End-to-end case for Programmatic download of DrugBank releases via drugbank-downloader (requires DrugBank access)
4/4 ✓
95
Canonical✅ Pass
You need to extract structured drug properties (e.g., identifiers, synonyms, ATC codes) from DrugBank XML for downstream analysis
The archived run for You need to extract structured drug properties (e.g., identifiers,... remained guidance-driven rather than command-driven.
Basic 36/40|Specialized 59/60|Total 95/100
✅A1The drugbank-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 A✅ Pass
You want to build and analyze drug–drug interaction (DDI) networks from DrugBank interaction records
The archived run for You want to build and analyze drug–drug interaction (DDI) networks... remained guidance-driven rather than command-driven.
Basic 34/40|Specialized 57/60|Total 91/100
✅A1The drugbank-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
89
Edge✅ Pass
Programmatic download of DrugBank releases via drugbank-downloader (requires DrugBank access)
This edge case stayed inside the documented workflow and remained instruction-led.
Basic 33/40|Specialized 56/60|Total 89/100
✅A1The drugbank-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
89
Variant B✅ Pass
XML parsing and traversal using lxml for reliable extraction of nested DrugBank entities
The archived run for XML parsing and traversal using lxml for reliable extraction of... remained guidance-driven rather than command-driven.
Basic 32/40|Specialized 57/60|Total 89/100
✅A1The drugbank-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
89
Stress✅ Pass
End-to-end case for Programmatic download of DrugBank releases via drugbank-downloader (requires DrugBank access)
The archived run for End-to-end case for Programmatic download of DrugBank releases via... remained guidance-driven rather than command-driven.
Basic 29/40|Specialized 60/60|Total 89/100
✅A1The drugbank-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 Total90.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 2/3; adjustment=3. analyze_interactions.py: OK; download_drugbank.py: rc=1; parse_xml.py: OK