CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

knn-imputation

Use when filtering genes with high missingness and then imputing missing values in a bulk expression matrix with group-aware KNN through DMwR2, where donor samples are restricted by one annotation column before imputation. For strata with 10 or fewer samples, the script falls back to row-wise direct filling with mean or median. NOT for: single-cell data, multi-column stratification, non-tabular inputs, network access, or interactive workflows.

Quality

88%

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 strong, highly actionable SKILL.md with a clear sequenced workflow, explicit validation and error-recovery loops, and well-signaled one-level-deep references. Weaknesses are modest: duplicated content (Workflow vs. Methods, two reference tables, error table vs. troubleshooting.md) and example commands that rely on test fixtures not shipped in the bundle.

Suggestions

Merge the trailing 'Reference Files' table into 'When to Read External Files' and consolidate the 'Methods' section with 'Workflow' — the 50% filter, ≥11-sample strata, and mean/median fallback rules are currently stated three times.

Ship the tests/data fixtures (sample_expression_matrix.csv, sample_groups.csv) with the skill, or rewrite examples to use placeholder user paths so the copy-paste commands are runnable.

Trim the inline error table to the few most common codes and defer the full catalog to references/troubleshooting.md to reduce duplication with that file.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence (no explanation of what KNN or CSV is), but contains redundancy: the "When to Use" section restates the description, the "Methods" section restates the "Workflow" section's filter/strata/fallback rules nearly verbatim ("Genes with at least 50% missing values are removed first... strata of 10 samples or fewer..."), and the reference-file table appears twice. This fits level 4 (efficient, minor instances that could be trimmed) rather than level 5 (every token earns its place).

4 / 5

Actionability

Concrete, copy-paste-ready Rscript invocations with every flag, a full argument table with defaults and types, executable examples, and local-validation commands. The gap keeping it from level 5: all example commands depend on `tests/data/sample_expression_matrix.csv` and `tests/data/sample_groups.csv` fixtures that are not present in the skill bundle (no tests/data directory exists), so the examples are not runnable as-is.

4 / 5

Workflow Clarity

A clear five-step sequence (Validate Input → Filter Genes → Build Strata → Run Imputation → Save Results) with explicit validation in Step 1, a stop condition ("Stop if all genes are removed by this filter"), a complete error-code table with causes and solutions, and an explicit escalation feedback loop ("IF error persists, READ: references/troubleshooting.md") plus output-verification commands in Local Validation. This matches the level-5 anchor (explicit validation steps, feedback loops for error recovery).

5 / 5

Progressive Disclosure

Good structure: a situation-to-file table routes to references/algorithm.md, scripts/main.R, references/troubleshooting.md, and references/cli-guide.md — all real files, verified one level deep (reference files do not cross-reference each other), and implementation scripts (functions.R, utils.R, etc.) are appropriately kept out of SKILL.md. Minor organization gaps keep it at level 4 rather than 5: the reference file table is duplicated verbatim at the bottom ("Reference Files" repeats "When to Read External Files"), and the inline error table substantially duplicates references/troubleshooting.md.

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.

An excellent description: concrete, comprehensive, third-person, with an explicit 'Use when' trigger and an explicit NOT-for boundary list. The only weakness is keyword breadth — a few natural synonyms (NA filling, .csv) are missing.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "filtering genes with high missingness", "imputing missing values in a bulk expression matrix with group-aware KNN through DMwR2", "donor samples are restricted by one annotation column", and "falls back to row-wise direct filling with mean or median" — with comprehensive coverage of the pipeline stages. It matches the level-5 anchor (multiple specific concrete actions, comprehensive) and clearly exceeds level 4, since there are no meaningful gaps in what the skill does.

5 / 5

Completeness

It opens with an explicit "Use when filtering genes with high missingness and then imputing missing values..." trigger clause and fully states what the skill does (KNN via DMwR2, single-column donor restriction, mean/median fallback for small strata), matching the level-5 anchor where both what and when are explicitly answered with concrete trigger phrases. It is not level 4 because the when-clause is already specific and concrete rather than needing more detail.

5 / 5

Trigger Term Quality

Good natural keyword coverage — "imputing missing values", "bulk expression matrix", "KNN", "missingness" — but common user variations like "fill in NAs", "missing data", or the ".csv" file extension are absent. It sits between the level-3 anchor (some relevant keywords, missing variations) and level 5 (comprehensive synonyms/extensions), fitting the level-4 anchor (good coverage, a few natural terms missing).

4 / 5

Distinctiveness Conflict Risk

The niche is precise (bulk expression matrix, group-aware KNN via DMwR2, single annotation column) and the explicit "NOT for: single-cell data, multi-column stratification, non-tabular inputs, network access, or interactive workflows" boundary minimizes wrong-skill triggering. This matches the level-5 anchor (clear niche, distinct triggers, minimal conflict) and is clearly better than level 4's "minor overlap risk".

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

awesome-med-research-skills/Data Analysis/knn-imputation/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.