CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cobrapy

Constraint-based reconstruction and analysis (COBRA) for metabolic models; use when you need to simulate growth/production, analyze flux ranges, or run knockout and medium studies from SBML/JSON/YAML models.

Quality

76%

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/Data Analysis/cobrapy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 COBRA-specific core (sections 1-5) is accurate and highly actionable with a runnable example, but it is buried in a generic template shell: duplicated section headers, boilerplate governance sections, and unlinked reference files. Removing the template padding and wiring the references in by name would substantially improve the skill.

Suggestions

Delete the generic template sections (the first 'When to Use'/'Key Features'/'Dependencies'/'Example Usage'/'Implementation Details' variants, 'Deterministic Output Rules', 'Completion Checklist', 'Scope Reminder') and keep only the COBRA-specific sections 1-5, eliminating the duplicated headers.

Replace the vague 'reference material available in references/' mentions with explicit named links, e.g. '**Workflows**: See [workflows.md](references/workflows.md)' and '**API reference**: See [api_quick_reference.md](references/api_quick_reference.md)'.

Make the 'Recommended Workflow' concrete for COBRA tasks: e.g., load model -> check solver status -> run the requested analysis (FBA/FVA/deletion/medium) -> validate results (e.g., verify solution status is 'optimal', sanity-check growth rate) -> report, instead of the current abstract four-step boilerplate.

DimensionReasoningScore

Conciseness

Roughly half the body is generic template padding: duplicated section headers (two 'When to Use', 'Key Features', 'Dependencies', 'Example Usage', 'Implementation Details'), plus 'Deterministic Output Rules', 'Completion Checklist', a 'Scope Reminder' that restates the description verbatim, and a 'Quick Validation' section that declares no validation is required. The COBRA-specific sections 1-5 themselves are lean and accurate, keeping this above a 1.

2 / 5

Actionability

The example script is complete and copy-paste runnable (load_model -> optimize -> pfba -> FVA -> single_gene_deletion -> medium edit -> sampling), and section 5 documents genuinely non-obvious API behavior such as re-assigning the full medium dict and using `with model:` for reversible edits.

5 / 5

Workflow Clarity

The 'Recommended Workflow' is abstract boilerplate ('select the documented execution path', 'run a final validation pass') with no COBRA-specific checkpoints, and the 'Quick Validation' section explicitly offers no verification step. Sequence is present but validation is implicit/missing, matching the anchor for a 3.

3 / 5

Progressive Disclosure

The bundle provides references/api_quick_reference.md and references/workflows.md, but the body never names or links them — only vague mentions like 'Reference material available in `references/` for task-specific guidance'. References exist but are not clearly signaled, and detail that belongs in those files (section 5 API specifics) is inlined.

3 / 5

Total

13

/

20

Passed

Description

87%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 names the domain, gives multiple concrete capabilities, and includes an explicit 'use when' trigger clause with distinct, domain-specific terms. The only weakness is missing common synonyms like 'FBA'/'flux balance analysis' that users would naturally say.

DimensionReasoningScore

Specificity

Lists several concrete actions ('simulate growth/production, analyze flux ranges, or run knockout and medium studies from SBML/JSON/YAML models') anchored in a named domain. Minor gaps in coverage (e.g., gapfilling, flux sampling, model construction) keep it below the comprehensive anchor.

4 / 5

Completeness

Explicitly answers both what (constraint-based reconstruction and analysis for metabolic models with concrete capabilities) and when ('use when you need to simulate growth/production, analyze flux ranges, or run knockout and medium studies'), matching the top anchor.

5 / 5

Trigger Term Quality

Good natural-term coverage ('growth', 'flux', 'knockout', 'medium studies', 'SBML/JSON/YAML'), but a few common terms users would say are missing, notably 'FBA' / 'flux balance analysis' and file extensions like .sbml.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (COBRA metabolic modeling) with domain-specific trigger phrases (FBA-style growth simulation, knockout/medium studies, SBML/JSON/YAML models) that no generic skill would match, so conflict risk is minimal.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Data Analysis/cobrapy/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.