CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pymoo

Solves and validates single-, multi-, and many-objective optimization with pymoo, including NSGA-II, NSGA-III, MOEA/D, constraints, Pareto approximations, reference directions, and ZDT/DTLZ benchmarks for engineering and research problems.

Quality

80%

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 ./skills/pymoo/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 well-structured, information-dense skill body with real executable code, decision tables, and an excellent one-level-deep reference architecture verified against the actual bundle. The main improvement opportunities are inlining one copy-paste-ready end-to-end example and consolidating version/date provenance into a single section.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — it does not explain what optimization or Pareto fronts are, and uses compact tables for algorithm selection. Minor instances could be trimmed: the Overview repeats the description's content, and pinned version/date notes ("pymoo 0.6.2", "reviewed 2026-10-01") appear in prose rather than a dedicated section. Not score 5 for those small trims; not score 3 because there is no genuinely unnecessary concept explanation or padding.

4 / 5

Actionability

Most guidance is executable: install command, `minimize()` call, `get_problem()` lookups, GA/SBX/PM configuration, and runnable script commands (`python3 scripts/single_objective_example.py`). Minor gaps: the flagship `minimize()` snippet uses placeholder `problem, algorithm, termination` rather than a copy-paste-ready end-to-end example, and the common-case workflows are delegated to references/quick_start_workflows.md rather than shown inline. Not score 5 because of those placeholders; not score 3 because the code shown is real, complete, and correct.

4 / 5

Workflow Clarity

Multi-step guidance is well sequenced: a numbered workflow index table maps use-cases to nine workflows, algorithm-selection tables are decision-ready, and validation checkpoints are present ("Check feasibility before plotting or selecting", report CV for least-infeasible results, re-evaluate candidates after normalization, compare multiple seeds at matched budgets). Not score 5 because the full step-by-step sequences live in the reference file and the troubleshooting section gives problem→remedy lists rather than validate→fix→retry loops; not score 3 because explicit validation guidance is woven throughout.

4 / 5

Progressive Disclosure

Exemplary structure: a concise overview, a workflow index table linking to references/quick_start_workflows.md (verified to exist), per-file descriptions for all eight reference files (all verified present), grep-based search patterns, and a scripts/ listing with exact run commands. References are one level deep, clearly signaled with "See:" pointers, and no content that belongs in a separate file is inlined. All referenced paths resolve to real bundle files.

5 / 5

Total

17

/

20

Passed

Description

71%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 dense, specific, third-person description that names the domain's key algorithms and benchmarks with comprehensive capability coverage. Its main weakness is the absence of an explicit "Use when..." trigger clause and natural synonyms like "genetic algorithm" or "Pareto front" that would improve retrieval.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user mentions pymoo, multi-objective or evolutionary optimization, Pareto fronts/trade-offs, NSGA-II/III, or ZDT/DTLZ benchmarks."

Add natural user phrasings such as "genetic algorithm", "evolutionary algorithm", "Pareto front", and "trade-off analysis" to broaden trigger-term coverage.

Consider trimming "for engineering and research problems" (weak context padding) in favor of the concrete when-to-use clause above.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete capabilities — "Solves and validates single-, multi-, and many-objective optimization", "NSGA-II, NSGA-III, MOEA/D, constraints, Pareto approximations, reference directions, and ZDT/DTLZ benchmarks" — with comprehensive coverage of the skill's scope in third person. This matches the anchor for multiple specific actions with comprehensive coverage; it is not score 4 because there are no notable gaps in capability coverage, only in trigger phrasing (a different dimension).

5 / 5

Completeness

The "what" is clear and concrete, but there is no "Use when..." clause or equivalent explicit trigger guidance — "for engineering and research problems" only weakly implies when to use it. Per the judging guideline, a missing explicit trigger clause caps completeness at 3. It is not score 4 because the when-guidance is implied rather than stated at all.

3 / 5

Trigger Term Quality

Good keyword coverage: "multi-objective optimization", "Pareto", "NSGA-II", "constraints", "ZDT/DTLZ" are terms users would naturally say when needing this skill. A few natural terms are missing — "genetic algorithm", "evolutionary algorithm", "Pareto front", "trade-off analysis", "pymoo" itself as a standalone trigger word. Not score 5 because the synonym coverage is not comprehensive; not score 3 because the included terms are natural user phrasings, not just jargon.

4 / 5

Distinctiveness Conflict Risk

The pymoo-specific algorithm and benchmark names (NSGA-II/III, MOEA/D, ZDT/DTLZ, Pareto) form a clear niche with minimal conflict risk among similarly-scoped skills. Minor overlap risk remains with general optimization skills (e.g., a SciPy minimize or generic solver skill) since "single-objective optimization" is a broad phrase a user might say for a non-pymoo need, so it sits between the 4 and 5 anchors, closer to 4.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

K-Dense-AI/scientific-agent-skills

Path

skills/pymoo/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.