CtrlK
BlogDocsLog inGet started
Tessl Logo

ml-engineer

Machine learning engineer expert for PyTorch, scikit-learn, model evaluation, and MLOps

49

Quality

53%

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 ./crates/openfang-skills/bundled/ml-engineer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and names specific, correct APIs and patterns, but it is instruction-only with no executable code examples and no explicit validation feedback loops in its workflows. It earns full marks on organization but is held back by the absence of copy-paste-ready guidance and checkpoints.

Suggestions

Add at least one executable code block for the core PyTorch training loop and one scikit-learn Pipeline example so guidance is copy-paste ready rather than described.

Add explicit validation checkpoints to the deployment/registry workflow (e.g., validate metrics against the held-out test set before promoting a model, with a revert step on regression).

Trim explanatory asides that restate known ML fundamentals (e.g., the logistic-regression-vs-neural-network and learning-rate-divergence justifications) to tighten token use.

DimensionReasoningScore

Conciseness

The body is mostly lean bullet-point guidance without explaining basic concepts, but several bullets add justifications Claude already knows ("a well-tuned logistic regression often outperforms a poorly configured neural network," "sudden large learning rates cause divergence") that could be trimmed, keeping it at the mostly-efficient level.

2 / 3

Actionability

It names concrete, real APIs and patterns (nn.Module, DataLoader, Pipeline, ColumnTransformer, GridSearchCV, classification_report, roc_auc_score, MLflow, 80/10/10 stratified split), but provides no executable code blocks—only prose describing code—so guidance is specific yet incomplete and not copy-paste ready.

2 / 3

Workflow Clarity

Sequences appear in "Common Patterns" (train-validate-test split, model-registry promotion stages) and pitfalls give guardrails, but there are no explicit validation checkpoints or fix-and-retry feedback loops for the multi-step processes described, leaving checkpoints implicit.

2 / 3

Progressive Disclosure

At roughly 35 lines with no references/scripts/assets bundle present, the content is a single well-organized file split into clear sections (Key Principles, Techniques, Common Patterns, Pitfalls), which meets the bar for a sub-50-line skill needing no external references.

3 / 3

Total

9

/

12

Passed

Description

50%

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 identifies a coherent ML-engineering niche with real tool names, but it lacks concrete enumerated actions and any explicit "Use when..." trigger guidance. It is competent but generic enough to risk overlap and to under-signal when Claude should invoke it.

Suggestions

Add an explicit trigger clause, e.g. "Use when training or evaluating models in PyTorch/scikit-learn, tuning hyperparameters, or setting up MLOps pipelines."

Replace the abstract "expert for ... MLOps" framing with concrete actions such as "train, evaluate, tune, and deploy ML models."

Add common natural trigger terms like "deep learning," "neural networks," "train models," and "track experiments" to improve user-match coverage.

DimensionReasoningScore

Specificity

Names the domain ("machine learning engineer") and concrete tools ("PyTorch, scikit-learn") plus some activities ("model evaluation, and MLOps"), but does not list multiple specific concrete actions like training, deploying, or tuning; it stops at domain and areas rather than enumerated actions.

2 / 3

Completeness

Clearly answers "what" (an ML engineer expert for the listed tools/areas) but provides no "Use when..." trigger clause, so per the guidelines completeness is capped at 2 with the "when" only implied.

2 / 3

Trigger Term Quality

Includes genuinely natural keywords ("PyTorch, scikit-learn, model evaluation, MLOps") a user would say, but misses common variations such as "deep learning," "train models," "neural networks," or "machine learning."

2 / 3

Distinctiveness Conflict Risk

The named tools (PyTorch, scikit-learn, MLOps) give it a recognizable niche, but broad terms like "model evaluation" could still overlap with general data-analysis skills, so it is somewhat specific rather than clearly conflict-free.

2 / 3

Total

8

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
RightNow-AI/openfang
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.