Direct REST API access to KEGG (academic use only). Pathway analysis, gene-pathway mapping, metabolic pathways, drug interactions, ID conversion. For Python workflows with multiple databases, prefer bioservices. Use this for direct HTTP/REST work or KEGG-specific control.
89
86%
Does it follow best practices?
Impact
93%
1.97xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Gene-to-pathway mapping workflow
Uses kegg_api module
0%
100%
kegg_find for gene lookup
0%
70%
kegg_link for pathways
0%
100%
kegg_get for pathway details
0%
100%
Gene ID format
100%
100%
Tab-delimited parsing
100%
100%
Pathway ID extraction
50%
100%
Human organism code
100%
100%
No raw HTTP calls
0%
100%
Error response handling
30%
20%
Compound search and pathway retrieval formats
Uses kegg_api module
0%
100%
Formula search option
100%
100%
Compound-to-reaction link
0%
100%
Reaction-to-pathway link
0%
100%
KGML single-entry constraint
100%
100%
Compound ID format
100%
100%
Local result caching
100%
100%
Glycolysis KGML file
100%
100%
Tab-delimited parsing
100%
100%
No raw HTTP construction
0%
100%
Drug interaction check and ID conversion
Uses kegg_api module
0%
100%
kegg_ddi for interactions
0%
100%
Drug ID format
100%
100%
Max entries constraint
100%
100%
kegg_conv for UniProt
0%
100%
Supported conversion target
100%
100%
kegg_get for drug entries
0%
100%
Tab-delimited conv parsing
100%
100%
No unsupported conversions
100%
100%
kegg_link for drug-gene targets
0%
0%
Error handling
42%
57%
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.