CtrlK
BlogDocsLog inGet started
Tessl Logo

building-classification-models

Build and evaluate classification models for supervised learning tasks with labeled data. Use when requesting "build a classifier", "create classification model", or "train classifier". Trigger with relevant phrases based on skill purpose.

36

Quality

33%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/ai-ml/classification-model-builder/skills/building-classification-models/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

0%

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

This skill is almost entirely boilerplate with no actionable content. It describes what a classification model builder would do in abstract terms but provides zero executable code, no specific library recommendations, no concrete workflows, and no real examples. The content reads like a marketing description rather than an instruction set for Claude.

Suggestions

Replace the abstract descriptions with concrete, executable Python code examples using specific libraries (e.g., scikit-learn) showing actual classification workflows from data loading through evaluation.

Remove all boilerplate sections (Overview, How It Works, Integration, Prerequisites, Instructions, Output, Error Handling, Resources) and replace with a concise quick-start code block and specific decision guidance (e.g., when to use logistic regression vs. random forest vs. gradient boosting).

Add explicit validation checkpoints: e.g., check class balance before training, verify train/test split, validate metric thresholds before reporting results.

Include a concrete end-to-end example with actual code showing data preprocessing, model training, cross-validation, and evaluation metric reporting.

DimensionReasoningScore

Conciseness

Extremely verbose with extensive padding. Explains obvious concepts Claude already knows (what classification is, what data quality means), includes vague boilerplate sections ('Output', 'Error Handling', 'Resources', 'Instructions') that add no actionable value, and the 'How It Works' section describes abstract processes rather than providing concrete guidance.

1 / 3

Actionability

No executable code, no concrete commands, no specific algorithms or libraries mentioned. The examples describe what 'the skill will' do in abstract terms rather than showing actual code. References a non-existent 'classification-model-builder plugin' without any concrete implementation details. The Instructions section is entirely generic boilerplate.

1 / 3

Workflow Clarity

The workflow steps are vague abstractions ('Context Analysis', 'Model Generation', 'Evaluation and Reporting') with no concrete commands, no validation checkpoints, and no error recovery loops. The examples describe intended behavior rather than actual steps to execute. No specific metrics thresholds or validation criteria are provided.

1 / 3

Progressive Disclosure

Monolithic wall of text with no references to external files and no bundle files to support it. Content is poorly organized with multiple redundant sections (Overview, How It Works, When to Use, Examples, Best Practices, Integration, Prerequisites, Instructions all covering similar ground at a shallow level). No clear navigation structure.

1 / 3

Total

4

/

12

Passed

Description

67%

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 covers the basics of what the skill does and when to use it, but suffers from moderate vagueness in its capabilities and includes a meaningless filler sentence ('Trigger with relevant phrases based on skill purpose') that adds no value. It would benefit from more specific actions and richer natural trigger terms covering common ML classification terminology.

Suggestions

Remove the filler sentence 'Trigger with relevant phrases based on skill purpose' and replace with additional natural trigger terms like 'predict categories', 'logistic regression', 'random forest', 'accuracy score', 'confusion matrix'.

Add more specific concrete actions such as 'perform cross-validation, tune hyperparameters, generate confusion matrices, compare model performance metrics'.

Include file type or data format triggers like 'labeled dataset', 'CSV with labels', 'training data with categories' to improve distinctiveness from other ML skills.

DimensionReasoningScore

Specificity

Names the domain (classification models, supervised learning) and some actions (build, evaluate, train), but lacks specific concrete actions like 'generate confusion matrices', 'perform cross-validation', 'tune hyperparameters', or mention of specific algorithms.

2 / 3

Completeness

Answers both 'what' (build and evaluate classification models for supervised learning tasks with labeled data) and 'when' (explicit 'Use when' clause with trigger phrases). The 'when' clause is present and explicit, though the last sentence is weak filler.

3 / 3

Trigger Term Quality

Includes some natural trigger phrases like 'build a classifier', 'create classification model', 'train classifier', but the final sentence 'Trigger with relevant phrases based on skill purpose' is vague filler that adds nothing. Missing common variations like 'predict categories', 'label prediction', 'logistic regression', 'random forest', 'accuracy', 'precision/recall'.

2 / 3

Distinctiveness Conflict Risk

Somewhat specific to classification tasks within ML, but could overlap with general ML/data science skills or regression modeling skills. The mention of 'supervised learning' and 'labeled data' helps narrow scope, but 'build a classifier' could still conflict with broader ML skills.

2 / 3

Total

9

/

12

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.

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

9

/

11

Passed

Repository
jeremylongshore/claude-code-plugins-plus-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.