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

47%

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 ./skills/bio/brenda-database/SKILL.md

Quality

Content

27%

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

The skill body is sprawling and repetitive with significant redundant content and conceptual filler, and it promises external references and helper scripts that are not actually bundled, undermining both conciseness and progressive disclosure. Actionability and workflow clarity are moderate but lack verification checkpoints and verified executable dependencies.

Suggestions

Collapse the nine capability sections and six workflows into a concise quick-start with a single canonical example, moving detailed per-function usage into separate reference files; cut explanations of concepts Claude already knows.

Create the referenced bundle files (references/api_reference.md and the scripts/*.py modules) or remove the broken references so progressive disclosure is one level deep and real.

Add explicit validation/verification checkpoints for batch SOAP operations (e.g., validate EC number format → query → check empty results → cache → handle Fault) to turn the prose best-practices into a feedback-loop workflow.

Dimension	Reasoning	Score
Conciseness	The ~700-line body is heavily padded: nine near-identical capability sections, six verbose workflow examples, and explanations of concepts Claude already knows (BRENDA overview, SOAP basics, rate-limiting basics), matching the verbose/padded anchor; not 2 because the bulk is unnecessary repetition rather than minor tightening.	1 / 3
Actionability	Provides concrete copy-paste-style Python, real BRENDA response-format examples, and parsing regex, but the imported modules (brenda_client, scripts.brenda_queries, brenda_visualization, enzyme_pathway_builder) are not present as bundle files, undercutting true executability; not 3 because key dependencies are unverified/absent, not 1 because guidance is concrete rather than abstract.	2 / 3
Workflow Clarity	Six named workflows provide clear sequences and an error-handling section, but there are no explicit validation/verification checkpoints or validate→fix→retry feedback loops for batch SOAP queries, which per the scoring notes caps this dimension at 2; not 1 because steps are listed and ordered.	2 / 3
Progressive Disclosure	The body is a monolithic wall of text and references files that do not exist — no references/, scripts/, or assets/ directories are present, yet it cites references/api_reference.md and several scripts/*.py modules — matching the broken/monolithic anchor; not 2 because there is no real file structure to navigate.	1 / 3
	Total	6 / 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 and clearly distinguishes the BRENDA enzyme-database niche, but it lacks an explicit "Use when..." trigger clause and only partially covers the natural keyword variations a user would actually say.

Suggestions

Add an explicit trigger clause such as "Use when researching enzyme kinetics (Km, kcat, Vmax), looking up reaction equations, or comparing enzymes across organisms for metabolic pathway analysis."

Broaden natural trigger terms to include phrasings users actually say, e.g. "enzyme data", "Km values", "enzyme lookup", "EC number", "substrate specificity".

Keep the third-person voice but consider trimming the trailing "for biochemical research and metabolic pathway analysis" purpose clause into the trigger clause for a tighter what/when structure.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Retrieve kinetic parameters (Km, kcat), reaction equations, organism data, and substrate-specific enzyme information" — matching the multiple-specific-actions anchor; not below 3 because no vague filler, and 3 is the scale ceiling.	3 / 3
Completeness	Strongly answers "what" (access BRENDA via SOAP API, retrieve kinetic parameters etc.) but has no "Use when..." or equivalent trigger clause, so per the guidelines completeness is capped at 2; not 3 because the when is only implied.	2 / 3
Trigger Term Quality	Contains relevant keywords like "kinetic parameters (Km, kcat)" and "metabolic pathway", but misses common natural variations a user would say (e.g. "enzyme data", "Km values", "enzyme lookup"); not 3 due to incomplete coverage and not 1 because several usable terms are present.	2 / 3
Distinctiveness Conflict Risk	Clearly a distinct niche — BRENDA enzyme database via SOAP API with kinetic-parameter triggers — unlikely to fire for unrelated skills; not 2 because the domain and terms are uniquely specific.	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
referenced_paths_exist	Referenced path issues: 4 missing	Warning

	Total	13 / 16 Passed

Repository: wu-yc/LabClaw
Path: skills/bio/brenda-database/SKILL.md
Commit: df37802

Reviewed: about 1 hour 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.