Professional heatmap beautification tool with automatic clustering and annotation tracks
Install with Tessl CLI
npx tessl i github:aipoch/medical-research-skills --skill heatmap-beautifierOverall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
33%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 identifies a specific domain (heatmaps) but reads more like a product tagline than a functional skill description. It lacks concrete actions, natural trigger terms users would say, and critically missing any guidance on when Claude should use this skill over alternatives.
Suggestions
Add a 'Use when...' clause specifying triggers like 'when user asks to create, style, or improve heatmaps' or 'when working with gene expression data, correlation matrices'
Replace 'beautification tool' with concrete actions: 'Customize colors, add row/column annotations, apply hierarchical clustering, adjust labels'
Include natural user terms and file formats: 'heatmap', 'visualization', 'matrix plot', 'dendrogram', '.csv', 'expression data'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (heatmap beautification) and mentions some features (automatic clustering, annotation tracks), but lacks concrete actions like 'create', 'customize colors', 'add labels', or 'export'. | 2 / 3 |
Completeness | Describes what it does at a high level but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'heatmap' which users would say, but 'beautification tool' is not natural user language. Missing common terms like 'visualization', 'data matrix', 'color scale', or file formats. | 2 / 3 |
Distinctiveness Conflict Risk | 'Heatmap' provides some specificity, but 'beautification' and 'annotation tracks' could overlap with general data visualization or plotting skills without clearer boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable code examples for heatmap generation with good parameter documentation. However, it's bloated with boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) that don't aid task execution, and lacks validation workflows for data processing. The content would benefit from trimming metadata and adding error handling guidance.
Suggestions
Remove boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Prerequisites duplicate) that don't help Claude execute the task
Add validation steps: how to verify input CSV format is correct before processing, and how to check output quality
Move the detailed parameter table and color schemes to a separate REFERENCE.md file, keeping only essential parameters in the main skill
Add error handling examples showing what to do when clustering fails or input data is malformed
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains significant redundancy - the features list duplicates information found in the usage examples, and sections like 'Risk Assessment', 'Security Checklist', 'Evaluation Criteria', and 'Lifecycle Status' add boilerplate that doesn't help Claude execute the task. The core content is reasonably efficient but padded with unnecessary metadata. | 2 / 3 |
Actionability | Provides fully executable Python code examples with clear import paths, complete parameter tables, and copy-paste ready command line usage. The code examples are concrete and include realistic data structures for annotations. | 3 / 3 |
Workflow Clarity | The skill presents a single-task workflow (create heatmap) clearly, but lacks validation checkpoints. For a tool that processes data files and generates outputs, there's no guidance on verifying input data format, handling errors, or validating output quality before finalizing. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections (Basic Usage → Annotated → Full Parameters), but everything is in one monolithic file. The extensive parameter table, color schemes, and input format documentation could be split into reference files. No external file references are provided. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
91%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Table of Contents
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.