creating-data-visualizations
Generate plots, charts, and graphs from data with automatic visualization type selection. Use when requesting "visualization", "plot", "chart", or "graph". Trigger with phrases like 'generate', 'create', or 'scaffold'.
51
41%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/ai-ml/data-visualization-creator/skills/creating-data-visualizations/SKILL.mdQuality
Discovery
82%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 is reasonably well-structured with a clear 'Use when' clause and good trigger terms specific to data visualization. Its main weaknesses are the inclusion of the generic trigger 'scaffold' which seems misaligned with visualization tasks and could cause conflicts, and the lack of more specific capability details (e.g., supported chart types, data formats, output formats).
Suggestions
Remove or replace the trigger term 'scaffold' which is more associated with code generation and could cause conflicts with other skills; consider adding visualization-specific terms like 'bar chart', 'line graph', 'scatter plot', 'histogram' instead.
Add more specific capabilities such as supported chart types, input data formats (CSV, JSON, dataframes), or output formats to increase specificity and distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (data visualization) and some actions ('generate plots, charts, and graphs', 'automatic visualization type selection'), but doesn't list comprehensive specific actions like supported chart types, data transformations, or output formats. | 2 / 3 |
Completeness | Clearly answers both 'what' (generate plots, charts, and graphs from data with automatic visualization type selection) and 'when' (explicit 'Use when' clause with trigger terms and phrases). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'visualization', 'plot', 'chart', 'graph', 'generate', 'create', 'scaffold'. These cover common variations of how users request data visualizations. | 3 / 3 |
Distinctiveness Conflict Risk | The trigger term 'scaffold' is generic and could conflict with code scaffolding skills. Similarly, 'generate' and 'create' are very broad verbs. However, the combination with 'plot', 'chart', 'graph' narrows the niche somewhat. The word 'scaffold' in particular seems misplaced for a visualization skill and could cause false triggers. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder with no actionable content. It contains no executable code, no specific library recommendations, no concrete examples, and no real workflow guidance. The entire body reads like a generic template filled with abstract descriptions of what a visualization skill would do, rather than providing Claude with the specific instructions needed to actually create visualizations.
Suggestions
Add concrete, executable code examples using specific libraries (e.g., matplotlib, seaborn) showing how to create common chart types like bar charts, scatter plots, and line graphs.
Replace the abstract 'How It Works' and 'When to Use This Skill' sections with a concise decision table mapping data characteristics to visualization types (e.g., categorical → bar chart, time series → line plot, two numeric variables → scatter plot).
Add a validation workflow: generate plot → save to file → verify file exists and is non-empty → report to user, with error handling for common failures like missing columns or incompatible data types.
Remove all generic template sections ('Integration', 'Prerequisites', 'Instructions', 'Output', 'Error Handling', 'Resources') that contain no skill-specific information and waste tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanations of things Claude already knows. Sections like 'How It Works', 'When to Use This Skill', 'Overview', 'Integration', and 'Best Practices' (which are tips for the user, not Claude) are all filler. The 'Instructions' section is completely generic and adds no value. Nearly every section explains concepts rather than providing actionable guidance. | 1 / 3 |
Actionability | There is zero executable code anywhere in the skill. No concrete library usage (matplotlib, seaborn, plotly), no code examples, no specific commands. The examples describe what 'the skill will' do in abstract terms rather than showing how to actually do it. The 'Instructions' section is entirely generic ('Invoke this skill when trigger conditions are met'). | 1 / 3 |
Workflow Clarity | The workflow steps are vague and abstract ('Analyze the data', 'Generate the visualization'). There are no validation checkpoints, no error recovery loops, no specific sequences with concrete commands. The numbered steps in 'How It Works' and 'Instructions' are generic descriptions, not actionable workflows. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files and no bundle files to support it. The 'Resources' section mentions 'Project documentation' and 'Related skills and commands' without any actual links or file paths. Content is poorly organized with many redundant sections that could be consolidated. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.