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

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./backend/cli/skills/databases/brenda-database/SKILL.md

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable examples and real bundle-file references, but it is overly long and repetitive, and its workflows lack the validation checkpoints expected for batch/rate-limited API operations.

Suggestions

Collapse the duplicated function listings: keep concise signatures in one place (e.g., the Helper Scripts section) and have Core Capabilities/Workflows reference them instead of re-declaring imports and calls.

Add explicit validation/retry checkpoints in the Common Workflows (e.g., verify credentials before querying, handle empty results, retry with delays on rate-limit faults) to lift workflow clarity.

Move the large Data Formats/Parsing and Troubleshooting sections into reference files so SKILL.md acts as a lean overview pointing one level deep.

Dimension	Reasoning	Score
Conciseness	The body is ~710 lines and repeatedly restates the same function signatures across Core Capabilities, Helper Scripts, and Common Workflows, plus many boilerplate print loops; mostly useful but could be tightened significantly.	2 / 3
Actionability	Provides fully executable, copy-paste-ready Python examples with real function names matching the bundle scripts, concrete BRENDA response formats, and specific install/auth commands.	3 / 3
Workflow Clarity	Six Common Workflows are sequenced, but none include explicit validate-then-proceed checkpoints or retry feedback loops for the batch, rate-limited, auth-dependent API operations, which caps workflow clarity at 2.	2 / 3
Progressive Disclosure	It correctly signals a one-level-deep reference (references/api_reference.md, which exists) and documents three real script files, but the body itself is a monolithic wall of duplicated inline content that should be split out.	2 / 3
	Total	9 / 12 Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, well-scoped, and unlikely to conflict with other skills, but it lacks an explicit 'when to use' trigger clause and broader natural-language keyword variations, capping completeness and trigger quality at 2.

Suggestions

Add an explicit 'Use when ...' clause naming natural triggers (e.g., 'Use when you need enzyme kinetic parameters (Km, kcat, Vmax), reaction equations, or substrate specificity data from BRENDA').

Include common plain-language variations users might say, such as 'enzyme kinetics', 'turnover number', 'EC number lookup', or 'enzyme database query'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions via the SOAP API — 'Retrieve kinetic parameters (Km, kcat), reaction equations, organism data, and substrate-specific enzyme information' — matching the top anchor for naming several specific actions.	3 / 3
Completeness	Clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance; per the guidelines, a missing explicit when caps completeness at 2.	2 / 3
Trigger Term Quality	Contains relevant domain terms (BRENDA, SOAP API, Km, kcat, kinetic parameters, metabolic pathway) but offers no plain-language variations or a 'Use when' trigger clause, so coverage of natural terms is incomplete.	2 / 3
Distinctiveness Conflict Risk	The niche is sharply defined — querying the BRENDA enzyme database via SOAP for kinetic/reaction data — making conflict with other skills unlikely, and it is written in third person.	3 / 3
	Total	10 / 12 Passed

Validation

81%

Warnings & errors only

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

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (719 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

	Total	13 / 16 Passed

Repository: synthetic-sciences/openscience
Path: backend/cli/skills/databases/brenda-database/SKILL.md
Commit: 52845c3

Reviewed: about 10 hours ago

Table of Contents

Discovery Implementation Validation

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.