upset-plot-converter
Convert complex Venn diagrams with more than 4 sets to clearer Upset plots
Install with Tessl CLI
npx tessl i github:aipoch/medical-research-skills --skill upset-plot-converter65
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
50%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 excels at specificity and distinctiveness, clearly defining a narrow visualization conversion task. However, it lacks explicit trigger guidance ('Use when...') which is critical for skill selection, and could benefit from additional natural language variations users might employ when requesting this functionality.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when the user has a Venn diagram with many overlapping sets, mentions Upset plots, or needs to visualize complex set intersections'
Include additional natural trigger terms such as 'set intersection', 'overlapping categories', 'UpSet chart', or 'set visualization' to capture how users naturally describe this need
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists a concrete, specific action: 'Convert complex Venn diagrams with more than 4 sets to clearer Upset plots'. It names the exact input (Venn diagrams with >4 sets), the output (Upset plots), and the purpose (clarity). | 3 / 3 |
Completeness | The description answers 'what' (convert Venn diagrams to Upset plots) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'Venn diagrams', 'Upset plots', and '4 sets', but misses common variations users might say such as 'set visualization', 'intersection plot', 'overlapping sets', or 'UpSet chart'. | 2 / 3 |
Distinctiveness Conflict Risk | This is a highly specific niche skill focused on a particular visualization conversion (Venn to Upset plots). It's unlikely to conflict with other skills due to its narrow, well-defined scope. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides excellent actionable code examples with clear input/output documentation, making it easy to use. However, it suffers from significant boilerplate bloat with template sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) that don't add value for this straightforward visualization task and waste tokens.
Suggestions
Remove or relocate the Risk Assessment, Security Checklist, Evaluation Criteria, and Lifecycle Status sections - these are template boilerplate that don't help Claude perform the task
Add a brief error handling note or validation step (e.g., 'Verify output file exists and has non-zero size')
Move the Notes section higher, as it explains the 'why' behind using Upset plots which is more valuable than the boilerplate sections
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes useful code examples but has unnecessary boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) that add significant token overhead without providing actionable guidance for the task. | 2 / 3 |
Actionability | Provides fully executable Python code examples with clear function calls, parameters, and realistic sample data. Both dictionary and list-based input methods are demonstrated with copy-paste ready code. | 3 / 3 |
Workflow Clarity | For a simple single-task skill, the workflow is clear (call function with data, get output file). However, there's no validation step mentioned for verifying the output plot was generated correctly or handling common errors. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but includes excessive inline boilerplate (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) that should either be removed or moved to separate documentation files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%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 | |
- 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.