CtrlK
BlogDocsLog inGet started
Tessl Logo

flux-analyzer

Analyse FBA flux distributions to extract biological insights. Covers gene essentiality, phenotypic phase planes, flux sampling, pathway-level aggregation, secretion product prediction, and production of publication- quality figures.

60

Quality

70%

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/flux-analyzer/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.

The body is highly actionable with complete, executable COBRApy workflows and useful domain conventions, organized into a clear seven-step pipeline. It is held back mainly by absent per-step validation checkpoints for batch operations and modestly over-explained prose intros.

Suggestions

Add explicit validation checkpoints after batch steps (e.g., assert essentiality CSV is non-empty, verify wt_growth > 0 before computing fractions) with fix-retry guidance to raise workflow clarity.

Move large code blocks into bundled scripts/ files and reference them from SKILL.md to improve progressive disclosure and token efficiency.

Trim the prose intros (Overview and per-step paragraphs) to the domain-specific essentials Claude would not already know.

DimensionReasoningScore

Conciseness

Mostly lean: each step pairs a brief, biology-specific intro with executable code and adds genuinely domain-specific knowledge (5% lethality criterion, PPP rationale). Minor over-explanation in the prose intros and Overview keeps it just below fully lean.

4 / 5

Actionability

Fully executable, copy-paste-ready Python blocks with specific COBRApy calls, named output files, thresholds, and plotting code covering the common cases across all seven analyses.

5 / 5

Workflow Clarity

A clear seven-step sequence exists with a helpful Common Failure Modes section, but batch/destructive operations (genome-wide deletions, multiple file writes) lack explicit per-step validate→fix→retry checkpoints, capping workflow clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

Well-organized with clear section headers and two reference tables, and no nested references. However the ~250-line body inlines substantial code that could be split into bundled scripts (none exist), leaving minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

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

The description is specific and clearly conveys what the skill does, but it omits any explicit "Use when" trigger guidance and relies on technical terminology over natural user phrasing. Strong on capability specificity, weaker on completeness and trigger-term naturalness.

Suggestions

Add a "Use when..." clause naming natural trigger phrases (e.g., "Use when analysing FBA results, computing gene essentiality, or predicting secretion products").

Include common synonyms and file extensions users might mention (e.g., "COBRApy model", ".json model", "flux solution") to improve trigger-term coverage.

Add a brief "when to use" alongside the "what" to lift completeness above the missing-trigger cap of 3.

DimensionReasoningScore

Specificity

Lists six concrete actions ("gene essentiality, phenotypic phase planes, flux sampling, pathway-level aggregation, secretion product prediction, and production of publication-quality figures"), giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Provides a clear "what" (analyse FBA flux distributions and the listed analyses) but no explicit "when" / "Use when" clause, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Contains relevant domain keywords ("FBA flux", "gene essentiality", "phase planes", "flux sampling") but leans technical and omits common natural-language synonyms or file extensions users might say; no "Use when" trigger phrasing.

3 / 5

Distinctiveness Conflict Risk

Targets a clearly distinct niche (FBA metabolic flux analysis) with specific triggers, leaving only minor overlap risk with adjacent metabolic-modelling skills; not yet a fully unique trigger set, so below 5.

4 / 5

Total

15

/

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.