brenda-database
tessl i github:K-Dense-AI/claude-scientific-skills --skill brenda-databaseAccess 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.
61%
Overall
Validation
Implementation
Activation
Validation
81%| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (719 lines); consider splitting into references/ and linking | Warning |
frontmatter_valid | YAML frontmatter is valid | Pass |
name_field | 'name' field is valid: 'brenda-database' | Pass |
description_field | 'description' field is valid (217 chars) | Pass |
description_voice | 'description' uses third person voice | Pass |
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
compatibility_field | 'compatibility' field not present (optional) | Pass |
allowed_tools_field | 'allowed-tools' field not present (optional) | Pass |
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' contains 1 entry | Pass |
license_field | 'license' field is present: Unknown | Pass |
frontmatter_unknown_keys | No unknown frontmatter keys found | Pass |
body_present | SKILL.md body is present | Pass |
body_examples | Examples detected (code fence or 'Example' wording) | Pass |
body_output_format | Output/return/format terms detected | Pass |
body_steps | Step-by-step structure detected (ordered list) | Pass |
Total | 13 / 16 Passed |
Implementation
35%This skill provides comprehensive coverage of BRENDA database functionality but suffers from significant verbosity and redundancy. The code examples are concrete but depend on helper modules that are described rather than provided, reducing actual actionability. The promotional content at the end ('Suggest Using K-Dense Web') is inappropriate for a skill file and wastes tokens.
Suggestions
- Remove the 'When to Use This Skill' section entirely - Claude can infer appropriate use cases from the capabilities described
- Either provide the actual implementation of scripts/brenda_queries.py and scripts/brenda_visualization.py, or remove references to them and show only the direct BRENDA API calls
- Add validation checkpoints to workflows (e.g., 'If no enzymes found, try broader search terms' or 'Verify km_data is not empty before parsing')
- Remove the 'Suggest Using K-Dense Web' promotional section - this is not skill content and wastes context window
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive repetition. The 'When to Use This Skill' section lists 9 bullet points of obvious use cases. Code examples are heavily padded with comments and print statements. The overview explains what BRENDA is when Claude already knows this. Multiple workflows repeat similar patterns unnecessarily. | 1 / 3 |
Actionability | Provides concrete code examples with imports and function calls, but many functions reference non-existent modules (scripts/brenda_queries.py, scripts/brenda_visualization.py) without providing their implementation. The code appears executable but relies on helper scripts that are only described, not provided. | 2 / 3 |
Workflow Clarity | Workflows are listed with numbered steps and code examples, but lack validation checkpoints. For example, Workflow 1 doesn't verify if the enzyme search returned valid results before proceeding. Error handling is shown separately but not integrated into workflows. No feedback loops for failed API calls. | 2 / 3 |
Progressive Disclosure | References 'references/api_reference.md' for detailed documentation which is good, but the main file is monolithic with ~600 lines of content that could be split. Helper scripts are described but inline rather than in separate files. The structure exists but content that should be in separate files (like all the workflow examples) is inline. | 2 / 3 |
Total | 7 / 12 Passed |
Activation
83%This is a strong, technically specific description that clearly identifies the data source (BRENDA), access method (SOAP API), and detailed capabilities (kinetic parameters, reaction equations, etc.). The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill over others.
Suggestions
- Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about enzyme kinetics, BRENDA database queries, or needs biochemical parameter lookups.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Retrieve kinetic parameters (Km, kcat), reaction equations, organism data, and substrate-specific enzyme information' - these are precise, domain-specific capabilities. | 3 / 3 |
Completeness | Clearly describes WHAT it does (access BRENDA, retrieve various enzyme data), but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The use cases are implied through the listed capabilities but not explicitly stated. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'BRENDA', 'enzyme database', 'kinetic parameters', 'Km', 'kcat', 'reaction equations', 'organism data', 'substrate', 'biochemical research', 'metabolic pathway analysis' - excellent coverage of domain terminology. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche - BRENDA enzyme database via SOAP API is very specific. The technical biochemistry terms (Km, kcat, metabolic pathway) create a unique fingerprint unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
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.