CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

brenda-database

Access BRENDA enzyme database via SOAP API. Retrieve kinetic parameters (Km, kcat), reaction equations, organism data, and substrate-specific enzyme information for biochemical research and metabolic pathway analysis.

Quality

69%

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

Quality

Content

63%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 is highly actionable — verified, copy-paste-ready code against real bundled scripts with clear sequencing — but it is bloated by heavy duplication between the Capabilities, Helper Scripts, and Workflows sections, and nearly all detail is inlined rather than progressively disclosed. Halving the length by merging duplicated sections and moving function catalogs to references would preserve all utility.

Suggestions

Delete or drastically shrink the 'Helper Scripts' section — it duplicates function listings and usage examples already shown in 'Core Capabilities'; a one-line pointer per script would suffice.

Move the full 'Common Workflows' code listings into a references file (e.g. references/workflows.md) and keep only one or two representative workflows inline.

Trim the 8-item generic 'Best Practices' list to the BRENDA-specific items (rate limiting, quota, wildcards) and cut troubleshooting bullets that duplicate the Authentication and Rate Limits sections.

DimensionReasoningScore

Conciseness

The 'Helper Scripts' section re-documents with usage examples nearly every function already demonstrated across the nine 'Core Capabilities' sections, and the six 'Common Workflows' (~150 lines) largely recombine the same calls — several hundred of ~700 lines are redundant, matching 'noticeably verbose; several unnecessary explanations or padded sections'. Not 3 because the duplication and generic best-practices padding go beyond 'some unnecessary explanation'.

2 / 5

Actionability

Every example is complete, executable Python calling real bundled functions (all named functions verified to exist in the scripts with matching signatures), with a concrete install command, env-var authentication setup, working-directory guidance, and a full try/except error-handling block. Specific examples cover the common cases, matching the copy-paste-ready anchor.

5 / 5

Workflow Clarity

Clear install → authenticate → query sequencing, and workflows include inline guards ('if enzymes:', 'if km_data:', "if parsed['km_value']:") plus explicit error handling for API faults. Not 5 because validate→fix→retry feedback loops live in a separate troubleshooting list rather than being integrated into the workflow steps; not 3 because sequences and most checkpoints are present and concrete.

4 / 5

Progressive Disclosure

The single reference file (references/api_reference.md) is real, clearly signaled, and one level deep — but ~250+ lines of per-function catalogs ('Helper Scripts') and full workflow listings are inlined in SKILL.md itself where they belong in reference files, matching 'content that should be separate is inline'. Not 4 because the bulk of detailed material is inline rather than split out with only key examples in SKILL.md.

3 / 5

Total

14

/

20

Passed

Description

66%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, third-person description with good domain trigger terms, but it answers only 'what' — invocation guidance is limited to a weak purpose clause, so Claude may not reliably select this skill when enzyme-kinetics questions arise. Adding an explicit 'Use when...' clause and a few synonyms would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks about enzyme kinetics, Km/kcat values, EC numbers, or enzyme data from BRENDA.'

Include common synonyms such as 'enzyme kinetics', 'EC number', and 'turnover number' to broaden natural trigger coverage.

Mention additional capabilities the skill provides (inhibitors, cofactors, optimal pH/temperature) for more comprehensive coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions in third person — 'Retrieve kinetic parameters (Km, kcat), reaction equations, organism data, and substrate-specific enzyme information' — but coverage has minor gaps (no mention of inhibitors, pH/temperature optima, or pathway construction that the skill actually provides). Not 5 because the action list is not comprehensive; not 3 because more than 1-2 concrete actions are named.

4 / 5

Completeness

The 'what' is clear (access BRENDA via SOAP API, retrieve specific data types), but the 'when' is only weakly implied by 'for biochemical research and metabolic pathway analysis' — there is no explicit 'Use when...' clause, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural domain keywords like 'BRENDA enzyme database', 'kinetic parameters (Km, kcat)', 'reaction equations', 'metabolic pathway analysis' are terms users would actually say. Not 5 because common variations such as 'enzyme kinetics', 'EC number', 'turnover number', or 'enzyme data' are missing.

4 / 5

Distinctiveness Conflict Risk

Naming the specific database ('BRENDA ... via SOAP API') and its distinctive data types carves a clear niche distinct from generic database skills. Not 5 because a user asking generically for 'enzyme data' or 'protein kinetics' could overlap with other bio-database skills.

4 / 5

Total

15

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (727 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

12

/

16

Passed

Repository

synthetic-sciences/openscience

Path

backend/cli/skills/databases/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.