CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

brenda-database

Programmatic access to the BRENDA enzyme database via the SOAP API; use when you need kinetic constants (Km, kcat, Vmax), reaction equations, enzyme properties (pH/temperature optima, stability), or enzyme discovery by EC/substrate/product.

Quality

70%

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/brenda-database/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%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 body has a sensible structure with a real one-level-deep reference and script, but it is padded with generic boilerplate sections and its examples do not match the shipped script — the Python example imports a nonexistent BrendaClient class and the validation step invokes an unsupported --help flag with a fabricated expected output. The core guidance is only partially executable as written.

Suggestions

Fix the Python example to match the actual script: import and call the module-level get_km_values(ec_number, organism) from scripts/brenda_queries.py (or add a BrendaClient class to the script), and remove the 'adjust function names' hedge and the nonexistent get_reactions call.

Replace the broken 'Quick Validation' step: the script takes positional arguments ('python scripts/brenda_queries.py 1.1.1.1 "Homo sapiens"'), so document that as the smoke test and drop the fabricated 'Result file: brenda_database_result.md / Validation summary: PASS/FAIL' expected output.

Cut the generic filler sections (When Not to Use, Required Inputs, Output Contract, Validation and Safety Rules, Failure Handling) down to BRENDA-specific guidance — e.g., where to get BRENDA credentials and how the '#'/ '*' delimited response format is parsed — to reclaim token budget.

DimensionReasoningScore

Conciseness

Roughly a third of the body is generic template filler that adds no BRENDA-specific knowledge: 'Do not use this skill when a simpler direct answer is more appropriate', 'Return a structured deliverable that is directly usable without reformatting', 'Keep the output safe, reproducible, and within the documented scope at all times'. The 'When Not to Use / Required Inputs / Output Contract / Validation and Safety Rules / Failure Handling' sections restate behavior Claude already knows, matching the 2 anchor ('noticeably verbose; several unnecessary explanations or padded sections'). Not 1: the Usage, Dependencies, and Implementation Details sections do carry real, non-obvious content.

2 / 5

Actionability

Concrete elements exist ('uv pip install zeep requests', the BRENDA_EMAIL/BRENDA_PASSWORD exports, 'python scripts/brenda_queries.py'), but the central Python example is not executable as written: 'from scripts.brenda_queries import BrendaClient' and 'client.get_km_values(ec_number="1.1.1.1")' — the shipped script has no BrendaClient class, no get_reactions function, and its get_km_values requires an organism argument. The body even concedes this with 'adjust function names to match scripts/brenda_queries.py', making it acknowledged pseudocode — matching the 3 anchor ('some concrete guidance but incomplete; pseudocode instead of executable code; missing key details'). Not 4: the primary example fails against the actual bundle; not 2: real commands and a real runnable script path are provided.

3 / 5

Workflow Clarity

A sequence exists (set credentials, run the script or call its functions, parse results) and 'Quick Validation' attempts a checkpoint, but it prescribes 'python scripts/brenda_queries.py --help', which the script does not support (it takes positional '<ec_number> <organism>' arguments), and its 'Expected output format' ('Result file: brenda_database_result.md', 'Validation summary: PASS/FAIL') is fabricated — the script prints parsed entries, not that. Checkpoints are present but broken/generic, matching the 3 anchor ('steps listed but validation gaps; checkpoints missing or implicit'). Not 4: no working validation command exists; not 2: the core query path is genuinely sequenced with dependencies and invocation shown.

3 / 5

Progressive Disclosure

Good structure verified against the actual bundle: the body stays an overview, API methods live one level deep in a real, clearly signaled file ('For a complete list of available API methods and parameters, see: references/api_reference.md'), and the script is referenced by a real existing path (scripts/brenda_queries.py). This matches the 4 anchor ('good structure; most content is appropriately placed; references mostly clear; minor organization gaps'). Not 5: references/api_reference.md documents SOAP method names but not the script's actual Python function signatures, and the 'Response Parsing' subsection duplicates implementation detail that already lives in the script.

4 / 5

Total

12

/

20

Passed

Description

82%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 what the skill does and when to use it, using concrete domain-native trigger terms with minimal conflict risk. Its only deductions are the second-person 'use when you need' phrasing (penalized per rubric guidelines) and a few missing natural synonyms such as 'turnover number' or 'inhibitors'.

DimensionReasoningScore

Specificity

The description names the domain ('Programmatic access to the BRENDA enzyme database via the SOAP API') and several concrete capabilities ('kinetic constants (Km, kcat, Vmax), reaction equations, enzyme properties (pH/temperature optima, stability), or enzyme discovery by EC/substrate/product'), a base 4 for several specific items with minor gaps. However, the rubric's judging guidelines mandate a 1-point specificity penalty for second-person voice, and 'use when you need kinetic constants' is second person ('you need') rather than the third-person pattern of the anchors ('Processes files'). Base 4 minus 1 = 3; not 4 because the penalty applies, not 2 because the enumerated capabilities remain concrete and domain-specific.

3 / 5

Completeness

It explicitly answers both the 'what' ('Programmatic access to the BRENDA enzyme database via the SOAP API' plus enumerated data types) and the 'when' ('use when you need kinetic constants (Km, kcat, Vmax), reaction equations, enzyme properties..., or enzyme discovery by EC/substrate/product') with concrete trigger phrases, matching the 5 anchor exactly. Not 4: the 'when' clause is explicit and specific, not merely present-but-could-be-more-explicit.

5 / 5

Trigger Term Quality

Good coverage of terms a researcher would naturally say: 'kinetic constants (Km, kcat, Vmax)', 'reaction equations', 'pH/temperature optima', 'stability', 'enzyme discovery', 'EC', 'substrate', 'product', 'BRENDA enzyme database' — matching the 4 anchor ('good keyword coverage; a few natural terms missing'). Not 5: common variations like 'turnover number', 'inhibitors', and 'enzyme kinetics' are absent; not 3: coverage goes well beyond 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

'BRENDA enzyme database via the SOAP API' with triggers like Km/kcat/Vmax and EC number forms a clear niche with distinct triggers and minimal conflict risk against generic data-access skills, matching the 5 anchor. Not 4: no meaningful overlap with closely related skills exists given the uniquely named database and its parameter vocabulary.

5 / 5

Total

17

/

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