CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

elastic-net-feature-selection

Use when selecting predictive genes or other molecular features from bulk expression matrices for binary case-vs-control classification with elastic net logistic regression, including coefficient path and cross-validation plots. Trigger keywords: elastic net, glmnet, feature selection, binary classification, lambda.min, lambda.1se. NOT for: survival/Cox modeling, multiclass outcomes, single-cell data, or non-expression tables.

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 CLI skill body with explicit validation, error feedback loops, and well-signaled one-level references. Its weaknesses are redundancy (the ridge/empty-output caveat stated three times, a Methods section re-teaching known concepts, a meta Implementation Checklist) and a dangling reference to a nonexistent tests/data/ bundle path.

Suggestions

Collapse the thrice-repeated alpha=0/ridge/empty selected_features.csv caveat into a single note (e.g., in Output Files), and trim the Methods section — the elastic net mechanics already live in references/algorithm.md.

Remove or shrink the self-referential Implementation Checklist and the 'Last updated | Version' footer; they consume context without guiding usage.

Either add the tests/data/ bundle (expression_matrix.csv, groups.csv, genes.csv) referenced by the navigation table, workflow Step 1, and Testing section, or remove those references — the checklist even claims 'Test data provided' but no tests/ directory exists.

DimensionReasoningScore

Conciseness

The Methods section explains elastic net/cv.glmnet mechanics Claude already knows ('Elastic net combines lasso (L1) and ridge (L2) penalties...'), the alpha=0 ridge/empty-selected_features note is repeated three times (Output Files table, Automatic Alpha Selection, Feature Selection Rule), the 16-line self-referential Implementation Checklist adds no user guidance, and a dated footer ('Last updated: 2026-04-20 | Version: 1.0.0') adds time-sensitive noise — this is 'some unnecessary explanation', not the 4 anchor's 'minor instances'.

3 / 5

Actionability

Fully executable, copy-paste-ready commands: a complete invocation with every argument, three variant examples (first run, fixed alpha, lambda.1se), help/test commands, and validation commands — matching the 5 anchor's coverage of common cases; not the 4 anchor since no key details are missing.

5 / 5

Workflow Clarity

A clearly sequenced 4-step workflow with explicit validation as Step 1 (file existence, empty-input rejection, label and sample-matching checks), an error table mapping SKILL_* codes to causes and fixes, and an explicit recovery loop ('IF error persists, READ: references/troubleshooting.md') — matches the 5 anchor including feedback loops for error recovery.

5 / 5

Progressive Disclosure

Strong structure — a 'When to Read External Files' situation→file→purpose table, one-level-deep real references (algorithm.md, cli-guide.md, troubleshooting.md), and conditional WHEN...READ directives in the workflow — but tests/data/ is referenced as a bundle path in three places and does not exist in the bundle (no tests/ directory), a dangling navigation target that keeps it below the 5 anchor's 'easy navigation'.

4 / 5

Total

17

/

20

Passed

Description

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

Excellent description: explicit use-when trigger with concrete keywords, a well-defined what, and a NOT-for boundary list that sharply limits conflict with adjacent skills. Only minor gap is a few missing natural synonyms (lasso, regularization) among trigger terms.

DimensionReasoningScore

Specificity

Multiple concrete, specific actions are listed: 'selecting predictive genes or other molecular features', 'binary case-vs-control classification', 'elastic net logistic regression', and outputs 'coefficient path and cross-validation plots' — comprehensive coverage of the niche, matching the top anchor rather than the 4 anchor's 'minor gaps'.

5 / 5

Completeness

Both 'what' (elastic net logistic regression feature selection from bulk expression matrices with coefficient path and CV plots) and 'when' ('Use when selecting predictive genes...') are explicitly stated with concrete trigger phrases, plus an explicit NOT-for boundary — clearly the 5 anchor.

5 / 5

Trigger Term Quality

Explicit trigger keywords are provided ('elastic net, glmnet, feature selection, binary classification, lambda.min, lambda.1se') — good natural-term coverage, but common synonyms like 'lasso', 'regularization', or 'gene selection' are missing, so it fits the 4 anchor ('a few natural terms missing') rather than the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

A clear niche (elastic net gene selection for binary classification on bulk expression matrices) with an explicit exclusion list ('NOT for: survival/Cox modeling, multiclass outcomes, single-cell data, or non-expression tables') gives minimal conflict risk, matching the 5 anchor's 'clear niche with distinct triggers'.

5 / 5

Total

19

/

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

aipoch/medical-research-skills

Path

awesome-med-research-skills/Data Analysis/elastic-net-feature-selection/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.