Evidence Insight
kegg-api
87100Total Score
Core Capability
88 / 100
Functional Suitability
11 / 12
Reliability
10 / 12
Performance & Context
8 / 8
Agent Usability
14 / 16
Human Usability
8 / 8
Security
10 / 12
Maintainability
10 / 12
Agent-Specific
17 / 20
Medical Task
15 / 20 Passed
88Access the KEGG database API to retrieve biological data (genes, pathways, compounds, drugs). Invoke when the user asks to search, list, or get details from KEGG
3/4
86Access the KEGG database API to retrieve biological data (genes, pathways, compounds, drugs). Invoke when the user asks to search, list, or get details from KEGG
3/4
86Access the KEGG database API to retrieve biological data (genes, pathways, compounds, drugs). Invoke when the user asks to search, list, or get details from KEGG
3/4
86Packaged executable path(s): scripts/kegg_client.py
3/4
86End-to-end case for Scope-focused workflow aligned to: Access the KEGG database API to retrieve biological data (genes, pathways, compounds, drugs). Invoke when the user asks to search, list, or get details from KEGG
3/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 | Scientific content remained anchored to fetched metadata or source-linked evidence in the legacy review. |
| Practice Boundaries | PASS | The package stayed in retrieval, extraction, or evidence-organization scope rather than drifting into unsupported interpretation. |
| Methodological Ground | PASS | The legacy audit preserved a method-grounded interpretation of the Access the KEGG database API to retrieve biological data (genes, pathways, compounds, drugs). Invoke when the user asks to search, list, or get details from KEGG workflow. |
| Code Usability | PASS | The legacy evaluation did not preserve a usability failure in the packaged retrieval path. |
Core Capability88 / 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
The legacy audit deducted points for kegg-api in agent usability.
14 / 16
88%
Human Usability
The legacy audit gave full marks to human usability for this package.
8 / 8
100%
Security
The legacy audit deducted points for kegg-api in security.
10 / 12
83%
Maintainability
A modest deduction remained in maintainability for kegg-api in the archived review.
10 / 12
83%
Agent-Specific
Related legacy finding for kegg-api: Stabilize executable path and fallback behavior. Some inputs only reached PARTIAL due to execution gaps or weak boundary handling
17 / 20
85%
Core Capability Total88 / 100
Medical TaskExecution Average: 86.4 / 100 — Assertions: 15/20 Passed
88
Canonical
Access the KEGG database API to retrieve biological data (genes, pathways, compounds, drugs). Invoke when the user asks to search, list, or get details from KEGG
3/4 ✓
86
Variant A
Access the KEGG database API to retrieve biological data (genes, pathways, compounds, drugs). Invoke when the user asks to search, list, or get details from KEGG
3/4 ✓
86
Edge
Access the KEGG database API to retrieve biological data (genes, pathways, compounds, drugs). Invoke when the user asks to search, list, or get details from KEGG
3/4 ✓
86
Variant B
Packaged executable path(s): scripts/kegg_client.py
3/4 ✓
86
Stress
End-to-end case for Scope-focused workflow aligned to: Access the KEGG database API to retrieve biological data (genes, pathways, compounds, drugs). Invoke when the user asks to search, list, or get details from KEGG
3/4 ✓
88
Canonical✅ Pass
Access the KEGG database API to retrieve biological data (genes, pathways, compounds, drugs). Invoke when the user asks to search, list, or get details from KEGG
The archived command path for Access the KEGG database API to retrieve biological data (genes,... was structurally clear, yet still placeholder-bound.
Basic 33/40|Specialized 55/60|Total 88/100
✅A1The kegg-api output structure matches the documented deliverable
❌A2The script execution path completed successfully for the documented case
✅A3The output stays fully within the documented skill boundary
✅A4The response quality is acceptable for the documented path
Pass rate: 3 / 4
86
Variant A✅ Pass
Access the KEGG database API to retrieve biological data (genes, pathways, compounds, drugs). Invoke when the user asks to search, list, or get details from KEGG
The Access the KEGG database API to retrieve biological data (genes,... workflow is specified, but the execution example still depends on unresolved placeholders.
Basic 31/40|Specialized 55/60|Total 86/100
✅A1The kegg-api output structure matches the documented deliverable
❌A2The script execution path completed successfully for the documented case
✅A3The output stays fully within the documented skill boundary
✅A4The response quality is acceptable for the documented path
Pass rate: 3 / 4
86
Edge✅ Pass
Access the KEGG database API to retrieve biological data (genes, pathways, compounds, drugs). Invoke when the user asks to search, list, or get details from KEGG
Access the KEGG database API to retrieve biological data (genes,... remains a defined path, although the preserved example command was not directly runnable because placeholder values were never resolved.
Basic 30/40|Specialized 56/60|Total 86/100
✅A1The kegg-api output structure matches the documented deliverable
❌A2The script execution path completed successfully for the documented case
✅A3The output stays fully within the documented skill boundary
✅A4The response quality is acceptable for the documented path
Pass rate: 3 / 4
86
Variant B✅ Pass
Packaged executable path(s): scripts/kegg_client.py
The archived command path for Packaged executable path(s): scripts/kegg_client.py was structurally clear, yet still placeholder-bound.
Basic 29/40|Specialized 57/60|Total 86/100
✅A1The kegg-api output structure matches the documented deliverable
❌A2The script execution path completed successfully for the documented case
✅A3The output stays fully within the documented skill boundary
✅A4The response quality is acceptable for the documented path
Pass rate: 3 / 4
86
Stress✅ Pass
End-to-end case for Scope-focused workflow aligned to: Access the KEGG database API to retrieve biological data (genes, pathways, compounds, drugs). Invoke when the user asks to search, list, or get details from KEGG
The Access the KEGG database API to retrieve biological data (genes, pathways, compounds,... workflow is specified, but the execution example still depends on unresolved placeholders.
Basic 26/40|Specialized 60/60|Total 86/100
✅A1The kegg-api output structure matches the documented deliverable
❌A2The script execution path completed successfully for the documented case
✅A3The output stays fully within the documented skill boundary
✅A4The response quality is acceptable for the documented path
Pass rate: 3 / 4
Medical Task Total86.4 / 100
Key Strengths
- Primary routing is Evidence Insight with execution mode B
- Static quality score is 88/100 and dynamic average is 73.6/100
- Assertions and command execution outcomes are recorded per input for human review
- Execution verification summary: Script verification 1/1; adjustment=5. kegg_client.py: OK