data-visualization-helper
Data Visualization Helper - Auto-activating skill for Visual Content. Triggers on: data visualization helper, data visualization helper Part of the Visual Content skill category.
34
0%
Does it follow best practices?
Impact
100%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/18-visual-content/data-visualization-helper/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an extremely weak description that essentially only restates the skill's name and category without providing any substantive information. It lacks concrete actions, natural trigger terms, explicit usage guidance, and any distinguishing characteristics that would help Claude select it appropriately from a pool of skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates bar charts, line graphs, scatter plots, heatmaps, and pie charts from tabular data or datasets.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user asks to visualize data, create a chart, plot a graph, make a histogram, or display data graphically.'
Include supported data formats or contexts to improve distinctiveness, e.g., 'Supports CSV, JSON, and inline data tables. Use for statistical visualizations, trend analysis charts, or data dashboards.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Data Visualization Helper' is a name, not a description of capabilities. There are no specific actions like 'create charts', 'generate plots', 'render graphs', etc. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. The description only states it's an 'auto-activating skill for Visual Content' without explaining what it actually does or providing explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'data visualization helper' repeated twice, which is not a natural phrase users would say. Users would more likely say 'chart', 'graph', 'plot', 'bar chart', 'scatter plot', 'visualize data', etc. | 1 / 3 |
Distinctiveness Conflict Risk | 'Visual Content' is extremely broad and could overlap with image generation, diagram creation, UI design, or any other visual skill. There is nothing to distinguish this from other visualization-related skills. | 1 / 3 |
Total | 4 / 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 an empty placeholder with no substantive content. It repeatedly references 'data visualization helper' without ever defining what that means or providing any actionable guidance. The entire body consists of boilerplate meta-descriptions that tell Claude nothing about how to actually perform data visualization tasks.
Suggestions
Add concrete, executable code examples for common data visualization tasks (e.g., creating charts with matplotlib/plotly, generating Mermaid diagrams, building presentation visuals).
Replace the abstract 'Capabilities' section with a quick-start workflow showing specific steps, tools, and commands for producing visualizations.
Include specific guidance on choosing visualization types based on data characteristics (e.g., time series → line chart, categorical comparison → bar chart) with concrete examples.
Add references to detailed sub-files for advanced topics like Mermaid syntax, chart customization, or presentation tooling rather than listing vague capabilities.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'data visualization helper' excessively, and contains zero substantive information about how to actually help with data visualization. | 1 / 3 |
Actionability | There are no concrete instructions, no code examples, no specific commands, no tool references, and no executable guidance whatsoever. The content only describes what the skill claims to do in abstract terms without showing how. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The 'Capabilities' section vaguely mentions 'step-by-step guidance' but never provides any. There are no validation checkpoints or sequences of any kind. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no references to external files, no structured navigation, and no meaningful organization of content. The sections that exist are all meta-descriptions rather than actual instructional content. | 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
c8a915c
- 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.