CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

heatmap-beautifier

Professional beautification tool for gene expression heatmaps, automatically adds clustering trees, color annotation tracks, and intelligently optimizes label layout.

Quality

59%

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 ./scientific-skills/Data Analysis/heatmap-beautifier/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body contains genuinely useful executable material (API examples, parameter table, data format specs, smoke check) buried under heavy template boilerplate and duplicated governance sections. Its biggest defects are verbosity from padded boilerplate and inconsistent entry points (conflicting CLI flags, an audit command using the wrong input type). Consolidating to one workflow and one accurate command surface, and moving boilerplate out, would substantially improve it.

Suggestions

Remove the generic governance boilerplate ('Output Requirements', 'Response Template', 'Output Contract', 'Inputs to Collect', 'Validation and Safety Rules', 'Risk Assessment', duplicate 'When to Use'/'Key Features' sections) and the circular 'See `## X` above' pointers, keeping only the heatmap-specific usage, parameters, and data-format content.

Reconcile the entry points: align the CLI examples with the documented flags ('--data-path'/'--output-path' vs the currently shown '--input'/'--output'), and replace the audit command's free-text string argument with a real CSV sample path.

Name and link the actual reference file (e.g. 'Runtime checklist: see references/runtime_checklist.md') instead of the generic '`references/` contains supporting rules', and consider moving the parameter table and color-scheme list into a reference file to slim SKILL.md.

DimensionReasoningScore

Conciseness

The description is restated three times (body intro, 'When to Use', 'Key Features'), and roughly half the file is generic governance boilerplate ('Output Requirements', 'Response Template', 'Output Contract', 'Risk Assessment', 'Validation and Safety Rules') plus circular no-op pointers like 'See `## Prerequisites` above for related details.', matching the 'noticeably verbose; several padded sections' anchor. Not 1 because the core usage, parameter, and data-format sections are substantive rather than explanations of concepts Claude already knows.

2 / 5

Actionability

Concrete executable material exists (full create_heatmap example with all parameters, parameter table, CSV format spec, py_compile smoke check), but the entry points conflict: the parameter table defines '--data-path'/'--output-path' while the CLI section uses '--input'/'--output', and the audit command passes a free-text sentence where a CSV path is required. Fits 'some concrete guidance but incomplete; missing key details'; not 4 because the flag mismatches make the documented commands non-executable as written.

3 / 5

Workflow Clarity

A 5-step 'Workflow' with an explicit py_compile validation checkpoint is present, but five overlapping workflow framings ('Workflow', 'Example run plan', 'Response Template', 'Output Contract', 'Inputs to Collect') duplicate and partially contradict each other, and the CLI vs Python API paths conflict. Fits 'steps listed but checkpoints missing or implicit' due to the muddled sequencing; not 4 because the duplication and entry-point conflicts leave real gaps.

3 / 5

Progressive Disclosure

The bundle provides references/runtime_checklist.md and scripts/main.py, but the body only says 'Reference material available in `references/`' generically without naming or linking the checklist file, while inlining the full parameter table, color-scheme list, and API reference in SKILL.md. Fits 'some structure; references present but not clearly signaled; content that should be separate is inline'; not 2 because clear section headers keep it navigable, not 4 because the single reference file is never surfaced.

3 / 5

Total

11

/

20

Passed

Description

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

The description does a solid job stating what the skill does with three concrete, domain-specific actions, but it entirely lacks a 'Use when...' trigger clause and misses the natural phrasings and synonyms a user would likely say. Adding an explicit trigger sentence with common terms would lift both completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user wants to beautify, cluster, or annotate a gene expression heatmap, or mentions expression matrices, clustering trees, or annotation tracks.'

Add natural synonyms and file formats users would mention, such as 'heatmap', 'expression matrix', and '.csv'.

DimensionReasoningScore

Specificity

Names the domain ('gene expression heatmaps') and three concrete actions ('adds clustering trees, color annotation tracks, and intelligently optimizes label layout'), matching the 'lists several specific actions; minor gaps' anchor. Not 5 because input/export capabilities are absent; not 3 because three distinct actions exceed the 1-2 action anchor.

4 / 5

Completeness

The 'what' is clear (beautify gene expression heatmaps by adding clustering trees, annotation tracks, and optimized labels) but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords like 'gene expression heatmaps', 'clustering trees', and 'annotation tracks' are present, but natural user phrasings ('cluster my data', 'annotate a heatmap', 'visualize an expression matrix') and file extensions (.csv) are missing, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

'Gene expression heatmaps' establishes a clear niche with distinct triggers, but generic 'beautification' wording leaves minor overlap risk with general plotting/visualization skills, fitting the 'mostly distinct; minor overlap risk' anchor.

4 / 5

Total

14

/

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

scientific-skills/Data Analysis/heatmap-beautifier/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.