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 description is essentially a placeholder with no substantive content. It lacks any concrete actions, meaningful trigger terms, or guidance on when to use the skill. It would be nearly impossible for Claude to reliably select this skill from a pool of alternatives.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates bar charts, line graphs, scatter plots, pie charts, and heatmaps from tabular data.'
Add a 'Use when...' clause with natural trigger terms like 'chart', 'graph', 'plot', 'visualize', 'bar chart', 'histogram', 'scatter plot', '.csv visualization'.
Remove the redundant duplicate trigger term and replace with diverse, natural keywords users would actually use when requesting data visualizations.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Data Visualization Helper' is a label, not a description of capabilities. There is no mention of what specific actions this skill performs (e.g., creating charts, plotting graphs, generating dashboards). | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it.' There is no explanation of capabilities and no meaningful 'Use when...' guidance beyond the auto-generated trigger line. | 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', 'histogram', 'visualize data', etc. The triggers are generic and redundant. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic — 'Visual Content' and 'data visualization' could overlap with charting tools, dashboard builders, image generators, or any number of other skills. There are no distinct triggers or niche identifiers to differentiate it. | 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 template/placeholder with no substantive content. It repeatedly references 'data visualization helper' without ever defining what that means or providing any actionable guidance. It contains zero code examples, zero concrete instructions, and zero useful information for Claude to act on.
Suggestions
Add concrete, executable code examples for common data visualization tasks (e.g., creating charts with matplotlib/plotly, generating Mermaid diagrams, building presentation visuals).
Define a clear workflow with specific steps, such as: assess data type → choose visualization → generate code → validate output, with explicit validation checkpoints.
Remove all boilerplate sections (Purpose, When to Use, Example Triggers) and replace with actionable content: specific chart types, code snippets, and tool-specific guidance for Mermaid, matplotlib, D3, etc.
Add supporting reference files (e.g., CHART_TYPES.md, MERMAID_GUIDE.md) and link to them from the main skill for progressive disclosure of advanced topics.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is almost entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'data visualization helper' excessively, and provides zero substantive information about how to actually create data visualizations. | 1 / 3 |
Actionability | There are no concrete code examples, no specific commands, no executable guidance, and no actual instructions for creating any kind of data visualization. Every section is vague and abstract. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. The 'Capabilities' section mentions 'step-by-step guidance' but provides none. There are no steps, no sequences, and no validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no references to supporting files, no structured navigation, and no bundle files to support it. There is no meaningful content to organize. | 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.