CtrlK
BlogDocsLog inGet started
Tessl Logo

metabolic-study-planner

Plan publishable constraint-based metabolic modelling studies when the user has a broad biological or metabolic-engineering topic but no concrete dataset, organism, model, or hypothesis. Selects feasible BiGG/COBRA models, objectives, perturbations, analyses, metrics, figures, and risk controls before FBA code is generated.

74

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 and well-structured, with concrete model IDs, templates, a scored feasibility gate, and clear per-archetype workflows including validation feedback loops. The only conciseness slack is an extraneous physics analogy that could be removed.

Suggestions

Remove the collider-process analogy line ('This is the MFA analogue of choosing a collider process and parameter scan before generating events.') to tighten conciseness toward the lean anchor.

DimensionReasoningScore

Conciseness

Assumes Claude's knowledge of FBA/pFBA/FVA and stays dense and domain-specific, but the collider-process analogy ('This is the MFA analogue of choosing a collider process and parameter scan') is extraneous padding that could be trimmed.

4 / 5

Actionability

Provides concrete, executable artifacts — named model IDs (iJO1366, iMM904, Recon3D, iNJ661), per-archetype step sequences, required-metrics lists, paper-claim templates, a study_card.md template, a scored feasibility gate, and a ready-to-run first topic covering common cases.

5 / 5

Workflow Clarity

Each archetype has a numbered plan, and the Feasibility Gate ('Proceed only if total score is at least 18/25. Otherwise choose a simpler organism...') is an explicit validation checkpoint with a feedback loop; the study-card gate and AutoResearchClaw stage sequence add further checkpoints.

5 / 5

Progressive Disclosure

A single-file, single-purpose skill with no bundle files, well-organized sections, no nested references, and all content (archetypes, templates, gates) appropriately inline — matching the well-organized-sections anchor for skills needing no external references.

5 / 5

Total

19

/

20

Passed

Description

92%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, complete, and distinct, clearly stating both the planning capability and the trigger condition for when to apply it. Trigger-term coverage is strong but could add a few user-natural synonyms like 'COBRApy' or 'flux analysis'.

Suggestions

Add natural synonyms users actually say ('COBRApy', 'flux analysis', 'genome-scale model', 'GSM') to broaden trigger-term coverage toward the comprehensive anchor.

Consider leading with the imperative verb form consistently or fully third-person voice to avoid the mixed 'Plan ... Selects ...' construction.

DimensionReasoningScore

Specificity

Enumerates concrete planning actions ('Selects feasible BiGG/COBRA models, objectives, perturbations, analyses, metrics, figures, and risk controls') with comprehensive coverage of the study-planning domain, matching the multiple-specific-actions anchor.

5 / 5

Completeness

Explicitly states both what ('Plan publishable... studies... Selects feasible... models, objectives...') and when ('when the user has a broad biological or metabolic-engineering topic but no concrete dataset...') with concrete trigger conditions.

5 / 5

Trigger Term Quality

Includes solid domain terms ('constraint-based metabolic modelling', 'metabolic-engineering', 'BiGG/COBRA', 'FBA') but omits natural synonyms a user would say such as 'COBRApy', 'flux analysis', or 'genome-scale model', so it sits just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche — the pre-code planning stage for users lacking a concrete dataset — which distinguishes it from sibling builder/simulator skills and minimizes conflict risk.

5 / 5

Total

19

/

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.