CtrlK
BlogDocsLog inGet started
Tessl Logo

scikit-learn

Machine learning in Python with scikit-learn. Use for classification, regression, clustering, model evaluation, and ML pipelines.

55

Quality

65%

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/scikit-learn/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%Scale 1-5

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

This skill is a comprehensive but overly verbose scikit-learn guide that explains many concepts Claude already knows (what algorithms do, when to use classification vs regression, benefits of pipelines). The executable code examples are a strength, providing concrete, mostly copy-paste ready workflows. The main weakness is poor token efficiency — the content reads more like a tutorial for a human beginner than a concise reference for an AI assistant, with significant redundancy between sections.

Suggestions

Cut all 'When to use' subsections, algorithm descriptions, and conceptual explanations (e.g., what classification is, benefits of pipelines) — Claude already knows these. Focus only on scikit-learn-specific syntax, patterns, and gotchas.

Remove the algorithm listing sections entirely and defer them to the reference files — the Core Capabilities section largely duplicates what the Reference Documentation section already points to.

Fix the installation typo ('uv uv pip install' should be 'uv pip install') and ensure the first Quick Start example defines X and y or notes they're assumed.

Add explicit validation steps within workflows, e.g., 'Check class distribution after splitting', 'Verify no NaN values remain after imputation', to create proper feedback loops.

DimensionReasoningScore

Conciseness

Extensively verbose for Claude's context. Lists every algorithm category, explains when to use classification vs regression, describes what pipelines prevent, explains what scaling does — all knowledge Claude already has. The 'When to Use This Skill' section, algorithm listings, 'Benefits' of pipelines, and 'When to use' subsections are largely unnecessary padding. The content could be cut by 60%+ while preserving all actionable value.

2 / 5

Actionability

Provides multiple executable code examples covering classification, pipelines, clustering, and common patterns. The Quick Start and Common Workflows sections have copy-paste ready code. Minor gap: the installation commands have a typo ('uv uv pip install') and X/y variables are assumed without definition in the first example, but overall the guidance is concrete and executable.

4 / 5

Workflow Clarity

The 'Building a Classification Model' and 'Performing Clustering Analysis' workflows are clearly sequenced with numbered steps and code at each stage. However, there are no explicit validation checkpoints or error-handling feedback loops — e.g., no step to check for data quality issues after loading, no validation of pipeline output, no 'if this fails, do X' guidance in the workflows themselves. The troubleshooting section partially compensates but is separate from the workflows.

4 / 5

Progressive Disclosure

References to 6 separate reference files and 2 scripts are well-signaled with file paths, but no bundle files were provided, so we can't verify they exist. The SKILL.md itself is very long (~350+ lines) with substantial content that belongs in those reference files (algorithm listings, best practices, troubleshooting) inlined rather than deferred. The reference documentation section is essentially a table of contents that duplicates information already presented in the Core Capabilities section.

3 / 5

Total

13

/

20

Passed

Description

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

This is a solid description that clearly identifies the domain (scikit-learn ML in Python) and lists key task categories. It would benefit from adding common synonyms like 'sklearn' and more natural user trigger phrases. The 'when' guidance exists but could be more explicit about user-facing scenarios.

Suggestions

Add common synonyms and variations like 'sklearn', 'train a model', 'predict', 'supervised learning', 'unsupervised learning' to improve trigger term coverage.

Expand the 'Use for...' clause into a more explicit 'Use when...' with user-facing triggers, e.g., 'Use when the user asks about training models, making predictions, or building ML pipelines with scikit-learn.'

DimensionReasoningScore

Specificity

Lists several specific ML actions (classification, regression, clustering, model evaluation, ML pipelines) which are concrete tasks. Minor gaps — doesn't mention feature engineering, preprocessing, hyperparameter tuning, or other common scikit-learn capabilities.

4 / 5

Completeness

Has a clear 'what' (machine learning in Python with scikit-learn) and a 'when' via 'Use for classification, regression, clustering, model evaluation, and ML pipelines.' The 'when' clause is present but could be more explicit with user-facing trigger phrases like 'Use when the user asks about training models or making predictions.'

4 / 5

Trigger Term Quality

Includes strong natural keywords like 'machine learning', 'Python', 'scikit-learn', 'classification', 'regression', 'clustering'. Missing common synonyms and variations like 'sklearn', 'train a model', 'predict', 'fit', 'cross-validation', or 'supervised/unsupervised learning'.

4 / 5

Distinctiveness Conflict Risk

Specifying 'scikit-learn' and 'Python' narrows the scope well, distinguishing it from deep learning (PyTorch/TensorFlow) or R-based ML skills. Minor overlap risk with general Python data science skills or other ML framework skills.

4 / 5

Total

16

/

20

Passed

Validation

72%

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

Validation8 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (522 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

8

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.