CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

kegg-database

Direct access to KEGG via the REST API for academic-only pathway/gene/compound/drug queries; use when you need precise HTTP-level control or targeted KEGG ID mapping.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Evidence Insight/kegg-database/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, highly actionable body with an executable end-to-end example, concrete batching and error-handling constraints, and well-signaled one-level-deep references. Its main weaknesses are duplicated function listings across two sections and the absence of an explicit retry/validation loop for batch operations.

Suggestions

Merge the 'Key Features' function list into the 'API-to-function mapping' section (or vice versa) so each function and its formats are documented once, cutting roughly 15-20 lines of duplication.

Add a short explicit feedback loop for batch operations, e.g., 'If a batch request returns 404, verify each ID with kegg_info and retry the failed IDs individually' to satisfy batch-operation validation expectations.

Move the detailed per-function documentation into references/kegg_reference.md (it duplicates the script's docstrings), keeping only signatures and one-line purposes inline in SKILL.md.

DimensionReasoningScore

Conciseness

The body is mostly efficient but includes avoidable duplication: all seven functions ('kegg_info', 'kegg_list', 'kegg_find', 'kegg_get', 'kegg_conv', 'kegg_link', 'kegg_ddi') are listed in 'Key Features' and then re-listed with descriptions in 'Implementation Details', and kegg_get's output formats ('aaseq', 'ntseq', 'mol', 'kcf', 'image', 'kgml', 'json') appear in both sections. This matches the anchor 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trim level above.

3 / 5

Actionability

The end-to-end example is fully executable copy-paste Python with real identifiers ('hsa:7157', 'p53', tab-delimited parsing with a guard clause), and the guidance includes concrete batching limits ('up to 10 entries', 'only 1 entry' for image/kgml/json), specific HTTP codes ('400', '404'), and real identifier formats ('map00010', 'cpd:C00002', 'dr:D00001'). Specific examples cover the common cases.

5 / 5

Workflow Clarity

The example demonstrates a clear multi-step sequence (find -> link -> get -> conv) with an inline validation guard ('if not first_line: raise RuntimeError'), and the constraints section defines error handling ('Treat non-200 responses as failures', backoff/retry advice). It falls short of the top anchor because batch operations (chunking lists of <=10 IDs) lack an explicit validate -> fix -> retry feedback loop; it is above anchor 3 because checkpoints and error-code guidance are present, not missing.

4 / 5

Progressive Disclosure

Both referenced bundle files exist (scripts/kegg_api.py and references/kegg_reference.md) and are signaled one level deep with clear purpose ('For detailed endpoint syntax, database lists, and species codes, consult: references/kegg_reference.md'). Minor organization gaps keep it below the top anchor: the inline API-to-function mapping duplicates content available in the script docstrings and reference file, and the function list itself is duplicated across two sections.

4 / 5

Total

16

/

20

Passed

Description

68%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A distinct, well-targeted description with an explicit 'use when' clause and good natural keywords, but its action coverage is thin relative to the skill's actual capabilities and the second-person 'use when you need' phrasing incurs a specificity penalty. Rewriting the trigger in third person with more enumerated actions would lift it.

Suggestions

Enumerate more concrete operations in the description (e.g., 'cross-references entries across KEGG databases, converts KEGG IDs to UniProt/PubChem/NCBI, and looks up drug-drug interactions') to raise specificity from listing only queries and ID mapping.

Rewrite the trigger clause in third person with user-facing phrasing, e.g., 'Use when the user mentions KEGG pathways, gene IDs, compound/drug lookups, or KEGG-to-UniProt/PubChem ID conversion' to remove the second-person penalty and sharpen trigger terms.

Add natural synonyms users would say — 'drug-drug interaction', 'cross-reference', 'pathway enrichment inputs' — to improve trigger term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Direct access to KEGG via the REST API') with two concrete actions ('pathway/gene/compound/drug queries' and 'targeted KEGG ID mapping'), matching the anchor for 1-2 concrete actions with coverage gaps (no linking, DDI, or sequence retrieval despite the skill supporting them). The 'use when you need precise HTTP-level control' clause is second-person voice, incurring the rubric's mandated 1-point reduction from the baseline of 3.

2 / 5

Completeness

Both parts are present: a clear 'what' ('Direct access to KEGG via the REST API for academic-only pathway/gene/compound/drug queries') and an explicit 'use when' clause. The 'when' is phrased around internal need ('when you need precise HTTP-level control') rather than concrete user triggers like 'when the user mentions KEGG IDs', keeping it below the top anchor.

4 / 5

Trigger Term Quality

Good keyword coverage: 'KEGG', 'REST API', 'pathway', 'gene', 'compound', 'drug', and 'ID mapping' are terms users would naturally say. A few natural terms are missing — UniProt/PubChem conversion targets, 'drug-drug interaction', and 'cross-reference' — so it does not reach comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche — direct KEGG REST API access with HTTP-level control — that is unlikely to fire for any other skill; KEGG-specific terms make conflict risk minimal.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Evidence Insight/kegg-database/SKILL.md

Reviewed

Table of Contents

Is this your skill?

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.