CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

metabolomics-workbench-database

Access NIH Metabolomics Workbench (4,200+ studies) via REST API. Query metabolites, RefMet nomenclature, MS/NMR data, m/z search, study metadata for metabolomics and biomarker discovery.

Quality

68%

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/Data Analysis/metabolomics-workbench-database/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 core API documentation is well-structured with abundant executable examples and correct offloading of detail to a clearly signaled reference file, but the skill is dragged down by ~60 lines of auto-generated template filler, duplicated When-to-Use sections, an irrelevant product-promotion section, and workflows lacking validation checkpoints. Removing the boilerplate and adding response-handling checkpoints would lift it substantially.

Suggestions

Delete the template-generated sections ("When to Use" boilerplate list, "Key Features", "Dependencies", "Example Usage" with the directory listing, "Implementation Details") and the trailing "K-Dense Web" promotional paragraph; they consume context without aiding execution.

Add validation checkpoints to the Common Workflows, e.g., check response status and confirm the RefMet match returned a standardized name before searching studies, and verify a study ID exists in the available-studies list before fetching its data.

Show minimal response handling in at least one example per section (e.g., `response.raise_for_status(); data = response.json()`) so snippets are fully executable end-to-end.

DimensionReasoningScore

Conciseness

Lines 11-54 are generic template boilerplate ("Use this skill when a data analytics task needs a packaged method instead of ad-hoc freeform output", "not explicitly version-pinned in this skill package. Add pinned versions if this skill needs stricter environment control", an "Implementation Details" section saying "See `## Overview` above" about a section that appears later), plus a promotional "K-Dense Web" paragraph and two duplicated When-to-Use sections. These are several padded sections that add no value, matching the 'noticeably verbose' anchor even though the core API content is fairly dense.

2 / 5

Actionability

Concrete, executable requests.get() examples with real URLs cover compound, study, refmet, moverz, metstat, gene, and protein contexts, and the three workflows give step-by-step code. Falls short of 5 because snippets never show response status checks or parsing, and some URLs are templated placeholders ("ST{ID}", "{regno}") that are not copy-paste runnable.

4 / 5

Workflow Clarity

The three Common Workflows present a clear numbered sequence (standardize name via RefMet, search studies, retrieve data), but there are no validation checkpoints such as verifying the RefMet match returned a result before searching, confirming a study ID exists, or checking response status before parsing. Sequence is present but checkpoints are missing or implicit.

3 / 5

Progressive Disclosure

The bulk API detail is appropriately placed in the real, one-level-deep references/api_reference.md, which is clearly signaled ("Load this reference file when you need detailed API specifications or when using less common endpoints"), while key examples stay inline. Minor gaps: the boilerplate sections and duplicated output-format content (repeated from the reference) slightly muddy navigation, keeping it below the 'easy navigation' anchor.

4 / 5

Total

13

/

20

Passed

Description

70%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 specific, distinctive description that names concrete capabilities of the Metabolomics Workbench REST API with good domain trigger terms. Its main weakness is the absence of any "Use when..." trigger clause, which caps completeness and leaves Claude without explicit guidance on when to invoke the skill.

Suggestions

Append an explicit trigger clause, e.g., "Use when the user mentions Metabolomics Workbench, RefMet, metabolite standardization, m/z or mass searches, or metabolomics study data."

Include a few natural synonym phrases such as "mass spectrometry search" or "metabolite identification" to broaden trigger coverage.

Consider mentioning gene/protein-metabolite association queries to close the coverage gap against the body's documented capabilities.

DimensionReasoningScore

Specificity

"Query metabolites, RefMet nomenclature, MS/NMR data, m/z search, study metadata" names several concrete, real API surfaces, matching the 'several specific actions; minor gaps' anchor. Not 5 because gene/protein query capabilities (documented in the body) are omitted from the description.

4 / 5

Completeness

The "what" is explicit ("Access NIH Metabolomics Workbench (4,200+ studies) via REST API..."), but there is no "Use when..." clause or equivalent trigger guidance anywhere in the description, which caps completeness at 3 per the rubric guidelines. Not 4 because the "when" is entirely absent rather than merely under-specified.

3 / 5

Trigger Term Quality

Natural domain terms are present ("metabolomics", "Metabolomics Workbench", "metabolites", "m/z", "biomarker discovery") and would be said by target users. Not 5 because common phrasings like "mass spectrometry search", "metabolite identification", or "lipidomics" are missing.

4 / 5

Distinctiveness Conflict Risk

"NIH Metabolomics Workbench", "RefMet nomenclature", and "m/z search" identify a clear niche with distinct triggers; no other plausible skill would collide with these terms.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Data Analysis/metabolomics-workbench-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.