CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

synthetic-biology

Synthetic biology design and simulation tools. Codon optimization, gene circuit ODE modeling with growth feedback, SBML model creation, bifurcation analysis, barcode sequencing fitness analysis, and therapeutic genome engineering. For metabolic modeling use cobrapy; for sequence tools use biopython.

Quality

73%

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 ./backend/cli/skills/biology/synthetic-biology/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 body with executable code and embedded validation/troubleshooting guidance. Its two weaknesses are the ~470 lines of inline implementation code that could be trimmed, and the complete failure to reference the four existing scripts/ modules that duplicate that code — leaving the bundle orphaned and wasting the skill's progressive-disclosure architecture.

Suggestions

Replace the six inline capability implementations with brief usage notes plus pointers to the corresponding bundle files, e.g. "Full implementations: scripts/codon_optimize.py, scripts/gene_circuit.py, scripts/sbml_model.py, scripts/bifurcation.py" — this both fixes the orphaned bundle and cuts ~470 lines of body code.

Move the 23-line inline E. coli codon usage table into a script or reference file, keeping only a one-line usage example in SKILL.md.

Make each snippet self-contained: import pandas inside sensitivity_analysis and define or reference toggle_switch explicitly in Workflow 2.

DimensionReasoningScore

Conciseness

The prose is lean and assumes Claude's domain competence, but ~470 lines of implementation code are inlined — including a 23-line E. coli codon table and full ODE/SBML/fitness implementations — that duplicate the 2,221-line scripts/ bundle, so the body could be substantially tightened. It is not 2 because there is no padding with concepts Claude already knows; the excess is structural (penalized under progressive_disclosure) rather than explanatory.

3 / 5

Actionability

A runnable Quick Start plus six largely copy-paste-ready capability blocks, three worked workflows, an install command, and a troubleshooting section give concrete executable guidance. It is not 5 because of minor gaps: sensitivity_analysis uses pd.DataFrame without importing pandas in that snippet, and Workflow 2 depends on toggle_switch being defined in Quick Start.

4 / 5

Workflow Clarity

Typical Workflows give concrete end-to-end sequences, Best Practices embed checkpoints ("always call doc.getNumErrors() after model creation", "always check GC content after optimization"), and Troubleshooting provides fix-retry feedback (e.g. "excess work" → switch to BDF/Radau). It is not 5 because the workflows read as worked code examples rather than step-numbered procedures with explicit validate-before-proceed gates.

4 / 5

Progressive Disclosure

Section structure is well-organized (Overview / When to Use / Capabilities / Workflows / Best Practices / Troubleshooting / Resources), but the four scripts/*.py bundle files (2,221 lines) are never referenced anywhere in the body — all of their functionality is re-inlined instead — matching the anchor "content that should be separate is inline" with references absent. It is not 2 because the structure itself is solid rather than minimal; it is not 4 because zero signaling of an existing bundle is more than a minor organization gap.

3 / 5

Total

14

/

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 specific, capability-dense description in third-person voice with excellent neighbor-skill disambiguation. Its main weakness is the complete absence of a "Use when..." trigger clause, which caps completeness and reduces its discoverability for users who describe tasks in natural language.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions codon optimization, toggle switches, repressilators, SBML models, gene circuit dynamics, or barcode/fitness sequencing analysis."

Include natural synonyms users actually say — "toggle switch", "repressilator", "synbio", "plasmid design" — alongside the current technical terms.

DimensionReasoningScore

Specificity

Six concrete named capabilities are listed — "Codon optimization", "gene circuit ODE modeling with growth feedback", "SBML model creation", "bifurcation analysis", "barcode sequencing fitness analysis", and "therapeutic genome engineering" — giving comprehensive, specific coverage of the skill's actions. It is not 4 because there are no meaningful gaps within the stated scope.

5 / 5

Completeness

The "what" is explicit and concrete, but there is no "Use when..." clause or equivalent trigger guidance; "For metabolic modeling use cobrapy; for sequence tools use biopython" is disambiguation routing, not a usage trigger. Per the judging guideline, a missing when-clause caps this dimension at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage ("codon optimization", "SBML", "bifurcation analysis", "barcode sequencing", "gene circuit"), but common user phrasings like "toggle switch", "repressilator", "synbio", and "plasmid" are absent. It is not 5 because synonyms and natural variations of the core terms are missing.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (synthetic-biology design and simulation) and explicitly routes the two nearest neighbors ("For metabolic modeling use cobrapy; for sequence tools use biopython"), minimizing wrong-skill triggers. It is not 4 because the neighbor disambiguation addresses precisely the overlap risk the lower anchor describes.

5 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (571 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository

synthetic-sciences/openscience

Path

backend/cli/skills/biology/synthetic-biology/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.