CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

65

Quality

79%

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

83%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, actionable skill body with a complete executable example, well-signaled one-level-deep references, and clear batch/error constraints. The only gap is the absence of an explicit validation/retry feedback loop for the batch operations it recommends.

Suggestions

Add an explicit validate-then-retry loop for batch operations (e.g., on non-200 or partial results: chunk, retry with backoff, re-check) to satisfy the feedback-loop expectation for batch/destructive workflows.

Trim the duplicated function descriptions between 'Key Features' and 'Implementation Details' to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is well-organized and assumes Claude's competence without explaining what KEGG or REST APIs are; a few API-to-function descriptions restate endpoint behavior that could be trimmed, but most tokens earn their place.

4 / 5

Actionability

It provides a fully executable end-to-end example with real function names, identifiers, and parsing logic, plus a detailed API-to-function mapping with concrete option values and batching limits.

5 / 5

Workflow Clarity

The example sequences find -> link -> get -> convert with inline validation, and practical constraints cover chunking and HTTP failures, but there is no explicit validate-then-fix retry loop for the batch operations the skill explicitly encourages.

4 / 5

Progressive Disclosure

The SKILL.md is a clear overview that delegates bulk detail to a real one-level-deep reference (references/kegg_reference.md) and a real script (scripts/kegg_api.py), both referenced explicitly, with appropriate inline structure and navigation.

5 / 5

Total

18

/

20

Passed

Description

75%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 focused, third-person description that clearly identifies the KEGG REST niche and supplies an explicit use-when clause. It is specific and distinct, but the trigger coverage and the 'when' scenarios could be broadened to fully comprehensive.

Suggestions

Expand the 'use when' clause to list more trigger scenarios (e.g., cross-database ID conversion, drug-drug interaction lookups, batch entry retrieval) to improve completeness and trigger-term quality.

Add common synonyms/identifiers users might mention (KO/orthology, enzymes, PubChem/UniProt mapping) so natural phrasings match the skill.

DimensionReasoningScore

Specificity

The description names several concrete actions ('pathway/gene/compound/drug queries', 'KEGG ID mapping', 'precise HTTP-level control') covering the core operations, though the action list is condensed rather than exhaustive.

4 / 5

Completeness

It states both what the skill does ('Direct access to KEGG via the REST API for academic-only...') and when to use it ('use when you need precise HTTP-level control or targeted KEGG ID mapping'), with the 'when' clause present but limited to two scenarios.

4 / 5

Trigger Term Quality

It surfaces natural domain terms users would say ('pathway', 'gene', 'compound', 'drug', 'KEGG ID mapping') with good coverage, but omits common synonyms like 'orthology/KO' or file/identifier variations.

4 / 5

Distinctiveness Conflict Risk

The KEGG-specific, academic-only, REST-API framing carves a clear niche distinct from general bioinformatics skills, with only minor overlap risk against broader biomedical data skills.

4 / 5

Total

16

/

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.

Validation15 / 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
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.