CtrlK
BlogDocsLog inGet started
Tessl Logo

fba-simulator

Run Flux Balance Analysis (FBA) and related constraint-based simulations using COBRApy. Covers standard FBA, parsimonious FBA (pFBA), Flux Variability Analysis (FVA), loopless FBA, gene/reaction knockouts, and carbon source swapping. Outputs flux distributions and CSV files.

63

Quality

75%

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 ./external/agents/Biology-Agent/skills/fba-simulator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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.

A highly actionable, well-structured workflow skill with copy-paste-ready code throughout; its main weakness is the absence of explicit validation checkpoints within the batch gene-deletion and carbon-swap steps, which caps workflow clarity.

Suggestions

Insert an explicit validation/verification step after batch operations (e.g. after single_gene_deletion and the carbon-source loop, check status columns and re-run or flag failures) to establish a feedback loop.

Trim the conceptual one-liners explaining what FBA/pFBA are, since Claude already knows these, leaving only the action-oriented rationale.

DimensionReasoningScore

Conciseness

Largely lean with executable code dominating each step, but includes brief concept explanations Claude already knows (e.g. 'FBA solves a linear program to find the flux distribution that maximizes...'), which could be trimmed.

4 / 5

Actionability

Every workflow step ships complete, copy-paste-ready COBRApy code with specific function calls, parameters (e.g. fraction_of_optimum=0.90, processes=4), and CSV output — fully executable with no pseudocode.

5 / 5

Workflow Clarity

The 9 steps are clearly sequenced, but batch/destructive operations (single_gene_deletion, multi-source carbon swapping) lack an explicit validate-then-retry checkpoint in the flow, which per the guidelines caps workflow clarity at 3 despite a helpful Common Failure Modes section.

3 / 5

Progressive Disclosure

Well-organized single-file structure with clear sections (Overview, 9 Workflow steps, Key Conventions, Output File Conventions, Common Failure Modes) and no nested references; minor gap is that some tabular reference material could be split out, though it is cohesive inline.

4 / 5

Total

16

/

20

Passed

Description

75%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 highly specific, well-scoped description with comprehensive action coverage and minimal conflict risk, weakened only by the absence of an explicit 'when to use' trigger clause and a few missing natural synonyms.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger scenarios, e.g. 'Use when running FBA, pFBA, FVA, knockouts, or carbon-source swaps on a COBRApy model.'

Include a couple of additional natural terms users say, such as 'metabolic model' and 'growth rate', and mention common model file extensions like .xml/.json.

DimensionReasoningScore

Specificity

Lists multiple concrete simulation actions — 'standard FBA, parsimonious FBA (pFBA), Flux Variability Analysis (FVA), loopless FBA, gene/reaction knockouts, and carbon source swapping' — giving comprehensive coverage with no vague filler.

5 / 5

Completeness

The 'what' is clear (runs constraint-based simulations, outputs flux distributions and CSV files), but there is no explicit 'Use when...' trigger clause, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Strong natural-term coverage including synonyms ('Flux Balance Analysis (FBA)', 'pFBA', 'FVA', 'COBRApy', 'knockouts', 'carbon source'), but missing a few natural variants users might say such as 'metabolic model', 'growth rate', or model file extensions (.xml/.json).

4 / 5

Distinctiveness Conflict Risk

Targets a distinct niche (constraint-based metabolic simulation via COBRApy) with specialized triggers unlikely to overlap with other skills, giving minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
aiming-lab/AutoResearchClaw
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.