CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

estimate-immune-score-analysis

Use this skill to compute ESTIMATE immune-related microenvironment scores from a bulk expression matrix, generate an ESTIMATE score heatmap, and optionally generate group-wise ESTIMATE score boxplots plus significance tables when a sample group file is supplied. Trigger keywords: ESTIMATE, immune score, stromal score, tumor microenvironment score. NOT for: immune cell deconvolution, single-cell analysis, differential expression, clinical diagnosis.

Quality

83%

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

67%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 well-structured CLI skill body with executable commands, complete argument/output/error tables, and exemplary external-file navigation. It is held back by duplicated scope sections, a development-facing checklist, and multiple references to a tests/ bundle (data and test scripts) that is absent from the provided files.

Suggestions

Remove the missing tests/ references or ship the files: the "When to Read External Files" table, the Testing section, and the data provenance note all point to tests/data/, tests/run_tests.R, and tests/test_skill.R, none of which exist in the bundle.

Merge the duplicated out-of-scope guidance: "When Not to Use" and "Do not use this workflow for" under Input Validation repeat nearly the same list (single-cell, deconvolution, clinical use); keep one section and the canned refusal message.

Trim token overhead by cutting the "Implementation Checklist" (development bookkeeping) and condensing "When to Use", which restates the frontmatter description; this lifts the body toward the leaner anchor-4 conciseness profile.

DimensionReasoningScore

Conciseness

The body is mostly dense, task-specific reference material (argument, output, and error tables), but there is noticeable tightening potential: the out-of-scope list appears nearly verbatim twice ("When Not to Use" and "Do not use this workflow for" under Input Validation), "When to Use" restates the frontmatter description, and the closing "Implementation Checklist" is development bookkeeping rather than execution guidance. This sits between anchor 2 (several padded sections) and anchor 4 (minor trims only), so 3 fits best.

3 / 5

Actionability

Guidance is largely copy-paste ready: full CLI invocations with all flags ("Rscript scripts/main.R --input_file ... --seed 42"), a complete argument table, concrete input/output examples, and per-error solutions. It misses anchor 5 because the Testing section and the bundled demo data point at files that are not present in the bundle ("tests/data/expression_matrix.csv", "tests/run_tests.R", "tests/test_skill.R"), so those commands are not executable as written.

4 / 5

Workflow Clarity

The Workflow section gives a clear validate → run ESTIMATE → export sequence with an explicit validation step (numeric columns, unique sample names) and documented failure-preserving behavior for grouped comparison, matching anchor 4's clear sequence with most checkpoints. It falls short of anchor 5 because post-run verification is relegated to an "Optional post-check" that references a missing test script, so the verify→fix→retry loop is not fully closed.

4 / 5

Progressive Disclosure

Structure is good: a "When to Read External Files" table maps situations to the real bundled files (references/algorithm.md, references/troubleshooting.md, references/cli-guide.md, scripts/main.R — all present) and references are one level deep, matching anchor 4. It is not a 5 because the body repeatedly points to a tests/ directory ("Need sample input files → tests/data/", plus the Testing section) that does not exist in the bundle, so navigation against the actual file listing has real gaps.

4 / 5

Total

15

/

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.

A strong description: it names the exact inputs (bulk expression matrix, optional sample group file), the concrete outputs (scores, heatmap, boxplots, significance tables), explicit trigger keywords, and explicit boundaries against adjacent skills. The only gap is a few missing natural trigger terms such as "tumor purity".

DimensionReasoningScore

Specificity

Quotes multiple concrete actions with inputs and conditions: "compute ESTIMATE immune-related microenvironment scores from a bulk expression matrix", "generate an ESTIMATE score heatmap", and "optionally generate group-wise ESTIMATE score boxplots plus significance tables when a sample group file is supplied". This matches the anchor for multiple specific concrete actions with comprehensive coverage; nothing is generic or abstract, so it does not fall to 4.

5 / 5

Completeness

Both what and when are explicitly answered: what via the concrete action list, and when via the explicit trigger guidance "Trigger keywords: ESTIMATE, immune score, stromal score, tumor microenvironment score" plus a "NOT for:" exclusion list. This matches anchor 5 (both what and when with concrete trigger phrases); a 4 would require the when clause to be only implicit or less specific, which is not the case.

5 / 5

Trigger Term Quality

Explicit trigger keywords are natural user phrasing: "ESTIMATE, immune score, stromal score, tumor microenvironment score" — good coverage matching anchor 4. It falls short of anchor 5 because common synonyms users actually say are missing, notably "tumor purity" (a primary output), "ImmuneScore/StromalScore" as named outputs, and "ESTIMATE score" as a standalone phrase.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (ESTIMATE scoring on bulk expression matrices) and conflict risk is actively minimized by the explicit exclusions: "NOT for: immune cell deconvolution, single-cell analysis, differential expression, clinical diagnosis". This matches anchor 5 — clear niche with distinct triggers and minimal overlap with adjacent skills like deconvolution or differential-expression workflows.

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/estimate-immune-score-analysis/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.