CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

kegg-api

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.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

50%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.

The skill has a genuinely useful core — accurate, executable operation documentation matching the packaged script — but it is buried in generic boilerplate that inflates token cost without adding knowledge. Reference navigation is vague and one validation checkpoint describes output the script does not produce.

Suggestions

Delete the template-filler sections ('When to Use', 'Key Features', 'Dependencies', 'Implementation Details', 'Recommended Workflow', 'Output Contract') or reduce them to a few lines, keeping only the KEGG-specific operations, usage, and examples that carry real content.

Replace the generic mentions of `references/` with a named, linked pointer such as 'See [KEGG_API_Manual.txt](references/KEGG_API_Manual.txt) for the full operation reference', and remove the Operations section content that duplicates that manual.

Correct the 'Quick Validation' expected output to match what `python scripts/kegg_client.py --help` actually produces (argparse usage text), and document the valid values for the `--option` flag (e.g., formula, exact_mass, image) found in the script.

DimensionReasoningScore

Conciseness

Roughly half the body is generic template padding that adds no KEGG-specific knowledge: 'Use this skill when the request matches its documented task boundary', 'Prefer this skill for repeatable, checklist-driven execution rather than open-ended brainstorming', 'Repository baseline for current packaged skills', and overlapping filler sections ('Key Features', 'Implementation Details', 'Recommended Workflow', 'Validation and Safety Rules') that repeat the same vague guidance. It is not a 1 because the Operations, Usage, and Examples sections do carry real content; it is not a 3 because the volume of boilerplate is substantial, not just occasional over-explanation.

2 / 5

Actionability

The Operations section documents all seven operations with usage strings and examples ('find genes shiga+toxin', 'get hsa:10458') that match the actual packaged script (verified against scripts/kegg_client.py's argparse choices), and the Examples section gives copy-paste-ready commands. It is not a 5 because '--option' is mentioned without documenting its valid values (formula, exact_mass, image exist only in the script), and 'See `## Usage` above' points to a section that appears later in the file.

4 / 5

Workflow Clarity

Steps are listed in 'Example run plan' and 'Recommended Workflow', but they are generic ('Produce the expected output using the documented file format') rather than KEGG-specific, and validation checkpoints are vague ('Run a final validation pass for completeness, consistency, and safety'). The 'Quick Validation' section's expected output ('Result file: kegg_api_result.md ... Validation summary: PASS/FAIL') does not match the script's actual '--help' behavior, so the checkpoint is fabricated. It is above a 2 because a real, runnable validation command exists and a sequence is present; it is below a 4 because checkpoints are non-specific and one is factually wrong.

3 / 5

Progressive Disclosure

The bundle does contain references/KEGG_API_Manual.txt, but the body only gestures at it generically ('Reference material available in `references/` for task-specific guidance', '`references/` contains supporting rules, prompts, or checklists') without ever naming the actual file, and the Operations section duplicates the manual's content inline. It is above a 2 because sections exist and the referenced directory is real; it is below a 4 because references are not clearly signaled or named and content that belongs in the reference file is inlined.

3 / 5

Total

12

/

20

Passed

Description

92%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 strong description: it states concrete capabilities with enumerated data types and pairs them with an explicit 'Invoke when...' trigger clause in third person. The only weakness is modest synonym coverage in trigger terms.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ('search, list, or get details') with an enumerated scope of data types '(genes, pathways, compounds, drugs)', comprehensively covering the skill's domain. It is not a 4 because there are no minor gaps within the skill's stated scope, and not below because every capability is stated as a concrete action rather than generic language.

5 / 5

Completeness

It explicitly answers 'what' ('Access the KEGG database API to retrieve biological data (genes, pathways, compounds, drugs)') and 'when' with a concrete trigger clause ('Invoke when the user asks to search, list, or get details from KEGG'). This matches the top anchor exactly; a 4 would require a less explicit or specific 'when' clause.

5 / 5

Trigger Term Quality

Natural user-facing terms like 'KEGG', 'search', 'list', 'get details', 'genes', 'pathways', 'compounds', and 'drugs' are present, matching what a user would actually say. It is not a 5 because common synonyms such as 'Kyoto Encyclopedia of Genes and Genomes', 'look up', 'enzyme', or 'ortholog' are missing; it is above a 3 because coverage goes well beyond merely relevant keywords.

4 / 5

Distinctiveness Conflict Risk

The description names a specific niche resource (the KEGG database API) with distinct triggers, so it is clearly distinguishable from other skills with minimal conflict risk. A 4 would require minor overlap with closely related skills, which is not the case here.

5 / 5

Total

19

/

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